When the app. pool recycles does it release the handle to the PHP dll ?
Try tweaking the recycling params, to see if you can find a sweat spot.
I'm not sure what the recycling of the IIS thread means in details, but the principal of eA is to keep php files cached during a "session". For example under Apache, when you cycle the threads unding fastcgi you loss all your ea cache, but it build up again quick on high traffic sites (so it's not really a problem). Maybe the php/ea handles/memory allocation also needs to be cleared when IIS recycles. Not sure if that an option under IIS...
A temp. option is to cycle the IIS service when traffic is lowest (middle of the night). Also try different version of php.
If I remember well 5.21 had some Windows "memory leaking" fixes. I think 5.21 is the first php5 version that seems a little faster the previous 5.x...just my impression...you might want to give it a try.
Joined: 2006-01-02
So it works fine until the app. pool recycles
When the app. pool recycles does it release the handle to the PHP dll ?
Try tweaking the recycling params, to see if you can find a sweat spot.
I'm not sure what the recycling of the IIS thread means in details, but the principal of eA is to keep php files cached during a "session". For example under Apache, when you cycle the threads unding fastcgi you loss all your ea cache, but it build up again quick on high traffic sites (so it's not really a problem). Maybe the php/ea handles/memory allocation also needs to be cleared when IIS recycles. Not sure if that an option under IIS...
A temp. option is to cycle the IIS service when traffic is lowest (middle of the night). Also try different version of php.
If I remember well 5.21 had some Windows "memory leaking" fixes. I think 5.21 is the first php5 version that seems a little faster the previous 5.x...just my impression...you might want to give it a try.
Cheers,
C