Apple

On Mar 17, 2011, at 9:58 AM, Frédéric JECKER wrote:

Hi,

We've rolled out a new feature in our app which includes an agenda (Jquery/FullCalendar).
The data loading is done through Ajax queries/DirectAction/JsonResponse.
Since then we are facing huge performance issues going from instance death to JVM crashes.
We first added a few more instances and allocated more memory to each instance (600M) but we are still facing
Those problems.

User are displaying up to 8 or ten agendas at the same time (each agenda containing a lot of events), which corresponds to 8 ajax queries each time the user browses to the next week/day/month. But multiplied with the number of concurrent users (min. 50 concurrent users), this start to produce a huge number of queries….

Googling a bit led me to the WOAllowsConcurrentRequestHandling and WOWorkerThreadCountMax parameters.
I think that we could get a lot of benefits with those parameters.
Are they working wit WO 5.3 ?
Help / Feedback on massive ajax querying would be greatly appreciated !

You probably want a higher WOWorkerThreadCountMax than normal, set this in JavaMonitor under Application Settings, Maximum Adaptor threads. I think the default is 128 so that should be plenty high enough.

Turning on WOAllowsConcurrentRequestHandling is always reccommended. You can set this in JavaMonitor under Additional Arguments, as -DWOAllowsConcurrentRequestHandling=true

I don't know if that will fix your problem, but it should help.

Chuck

Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.

http://www.global-village.net/products/practical_webobjects

References:
	>Ajax / DirectActions and performance issues (From: Frédéric JECKER <email@hidden>)