This page is to talk about the way of BOSS performance testing.
We created the test suit(http://gitorious.org/boss-performance-test) including:
In this case set, we executed following cases:
* Request 5000 workflows repeatly(send another 5k workflows to engine after previous 5000 finished); Repeat 20 times(100k workflows will be handled totally)
* Request 1000 workflows repeatly(send another 1k workflows to engine after previous 1000 finished); Repeat 100 times(100k workflows will be handled totally)
From above results, we can find some interesting things:
* Rates are almost NOT decreasing(for 1k or 5k, they are both around "25") * CPU/DISK is at high rate during testing * Memory is still taken after workflow finished. It looks like "memory leak" but it may not be if considering the "warm cache(or GC)" in Ruby/Python like language * NO workflow losing * NO engine crashing
This bug fix the channel closing issue, and solved following issues found before(http://wiki.meego.com/User_talk:Pennymax): * Crash * Workflow losing * Performance decreasing after running a while