Hi , 'in-memory' modification really helped to increase the throughput to a large amount. Many thanks for that comment. However, what we noticed was that the number of concurrent threads exist inside ODE is very small. For example lets say a service invocation executes in 100ms and if we apply 40 request/sec only 4 threads or workers will be needed to cater that workload.But, the following two cases saturates the sever significantly, making response time to grow large. 1) If we go beyond 40 req/sec 2) if the service execution time is 200ms and if we apply around 20 req/sec. (this also means that there is only 4 workers in the scheduler theoretically).
Is there a way to increase the concurrency level in ODE. After going through the code we found that the PROP_THREAD_POOL_SIZE = integer.max. However, the statistics shows that there is a significantly less threads serving the incoming requests. Please help us to understand this behaviour or configure the ODE so more threads can exist in the server concurrently. Regards Pati On Sun, Feb 5, 2012 at 3:53 AM, abdulkadir yaman <[email protected]>wrote: > Hi, > Do you need persitence capabilities for your Bpel flows? > In case you do not need, consider in memory flows and disable default event > generation strategy. take a look at link below for in-memory tag. > > http://ode.apache.org/creating-a-process.html > > On 4 Feb 2012 18:14, "Tharindu Patikirikorala" <[email protected]> > wrote: > > HI All, > > I am installed ODE in a single instance and then deployed a BPEL process > which communicate with 3 simple services. Although, the execution time of > this process is quite low (400 ms), the throughput (request/sec) from ODE > is 5 requests/sec, which is very low. Is there a way to tune ODE to > process more requests. > > Appreciate any comment, this is for academic purposes. > > > Thank you > Regards > Pati >
