This is my experience with OSWorkflow and it may not be conclusive. If you have better suggestions, please do let me know.
I use JMeter to load test OSWorkflow with 60 concurrent threads using a Unix Server with 16GB of RAM and 8 CPUs.
The workflow used is very simple. There are 3 steps, each steps only add and remove values from the Map set through the PropertySet.
Here are the results
I used the MemoryWorkflowStore in this case. The performance is ok initially but overtime the CPU usage goes up until the process crashes and core dump.
Look like something is taking the resources overtime. Audit trail maybe ? I am yet to read the source code.
So, how do I use OSWorkflow for a high transaction system…?