Are you using in-memory or persistent processes? How do you determine most of the CPU time is spent in Ode? In what parts specifically?
On my dual-core laptop I easily get 100+ TPS with in-memory processes, so my guess is you have a bottleneck somewhere else. The hard part, of course, it to find where! alex On 7/18/07, Vishal Bhasin <[EMAIL PROTECTED]> wrote:
Hello All, We are performing load tests on the orchestration we have built using ODE (1.0) and ServiceMix (3.2-incubating). Test Case: Receive request from JMS Consumer, process simple business rule (using Drool) and make 3 external Web Services calls (using HTTP Provider) that returns a response very quickly (within 50 millisecs). The responses from the 3 Web Services is normalized in an XML using XSLT. Orchestrated XML response size is around 50KB Environment 4 CPU AMD Opteron 64-bit, Advanced Server version 4 release 2 update 2, Jave 5 update 11. Results We are unable to go beyond 16 TPS (transactions per second), with CPU over 90%. We discovered that most of the time is spent within ODE SU. Obviously, this number is very low, is there anything that we can do to tune ODE? Thanks, Vishal Regards, Vishal Bhasin
