well that's a pretty solid point.  I had thought it was already "huge" but I 
suppose I can exert some pressure now.

On Jul 29, 2011, at 10:54 AM, Pascal Robert wrote:

> 
> Le 2011-07-29 à 10:50, Andrew Kinnie a écrit :
> 
>> Is that something I would put in the Application constructor?  Should that 
>> be in a property somewhere?
> 
>   public Application() {
>     ERXApplication.log.info("Welcome to " + name() + " !");
>     /* ** put your initialization code in here ** */
>     setAllowsConcurrentRequestHandling(true);
>   }
> 
>> As for the rest, it appears the issue is in the WO app instance.  Requests 
>> that go to the second instance seem to have normal response times.  My IT 
>> guy says the entire db is less than 60 MB, so MySQL seems not to be a 
>> problem.  Apparently we're not using Huge, but there don't seem to be any 
>> indications of a memory issue with MySQL.
> 
> The database might not be big, but it could be I/O performance problems. And 
> your server have tons of RAM, go ahead and tune MySQL right away, why wait 
> when you can do it now.
> 
>> On Jul 29, 2011, at 10:40 AM, Pascal Robert wrote:
>> 
>>> First question: does concurrent request handling 
>>> (application.setAllowsConcurrentRequestHandling(true)) is enabled? If not, 
>>> just enabled that and you will probably fix most of the performance 
>>> issues...
>>> 
>>> After that, you need to get metrics to find out where the bottleneck is... 
>>> Bandwith? CPU? RAM? The WO app? MySQL? One thing for sure, make sure that 
>>> MySQL is at least configured with the "huge" sample configuration file. If 
>>> MySQL is not currently using more than 512 MB, you are not using the "huge" 
>>> configuration file. Nagios plugins would be useful to gather the metrics.
>> 
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to