Poker Forum > General Discussion

Forum Performance

<< < (2/7) > >>

Des:
I"ve now got to wait for the server provider to complete some tasks tomorrow and we should be good to go.  Apologies once again for the inconvenience this downtime has caused.

technolog:

--- Quote from: duke3016 on January 13, 2012, 15:43:43 PM ---

--- Quote from: Des on January 13, 2012, 15:26:56 PM ---
CPU usage stats are holding steady, we may have nailed the problem.  (Famous last words.)



--- End quote ---


Just in time as well, Paulie was getting told off for deleting posts on Facebook....

--- End quote ---


;D

PHIL_TC:
Hi Des

Couldn"t access the forum last night and this morning, might just be me, but was getting a random time out or a "The FastCGI pool queue is full" error message.

Having hosted some random WordPress sites (presuming the APAT site is WordPress based?... if not ignore I ever posted this!) in the past before for companies I know we had to tweak some of the settings within the fcgiext.ini to increase the default values on :

1. instanceMaxRequests :  This is the max number of requests that can be processed by each FastCGI worker process before it is recycled.  The default value on install is 200.

2. maxInstances :  This is the max number of FastCGI worker processes that can be started in the application pool that is allocated to your website (we use IIS running over Windows here).  The default value on install is 4.

3. queueLength : This is the max number of requests that can be queued for a FastCGI process pool. The default value on install is 1000.

We also had a problem when a user added a widget plugin to their WordPress site, it had been fine then the CPU usage went crazy and we had to constantly recycle the application pool until we did more digging. It was a plugin called "WordPress Popular Posts" which was the culprit. Soon as we disabled the plugin, recycled the application pool, gave it the old "switch it all off and back on again" routine... it was fine.

Not sure if the above will help.... but just in case :)

Phil x

AMRN:

--- Quote from: PHIL_TC on January 18, 2012, 12:32:50 PM ---
Couldn"t access the forum last night and this morning, might just be me
--- End quote ---


Nope, not just you....

nosey-p:

--- Quote from: PHIL_TC on January 18, 2012, 12:32:50 PM ---
Hi Des

Couldn"t access the forum last night and this morning, might just be me, but was getting a random time out or a "The FastCGI pool queue is full" error message.

Having hosted some random WordPress sites (presuming the APAT site is WordPress based?... if not ignore I ever posted this!) in the past before for companies I know we had to tweak some of the settings within the fcgiext.ini to increase the default values on :

1. instanceMaxRequests :  This is the max number of requests that can be processed by each FastCGI worker process before it is recycled.  The default value on install is 200.

2. maxInstances :  This is the max number of FastCGI worker processes that can be started in the application pool that is allocated to your website (we use IIS running over Windows here).  The default value on install is 4.

3. queueLength : This is the max number of requests that can be queued for a FastCGI process pool. The default value on install is 1000.

We also had a problem when a user added a widget plugin to their WordPress site, it had been fine then the CPU usage went crazy and we had to constantly recycle the application pool until we did more digging. It was a plugin called "WordPress Popular Posts" which was the culprit. Soon as we disabled the plugin, recycled the application pool, gave it the old "switch it all off and back on again" routine... it was fine.

Not sure if the above will help.... but just in case :)

Phil x

--- End quote ---


What he said  :-\

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version