So its not just me then!
Their guys looked into it for me but we never arrived at a solution. Like Supercod, we got ourselves another server for running espot sites as the server would fall over quite a bit in high traffic times. (One day it was literally every 10 mins from about 11am to just after lunch)
It must cost them a small fortune if it isn't just affecting us - sometimes I was getting somewhere between 1 in 10-20 requests coming back with no results when I know there should be, if that isn't just limited to us then its gotta be costing.
I agree with you Supercod - the amount they are losing from returning no results (probably just off one or two of us guys!) is surely more than it would cost to fix it.
Something I have considered doing is knocking up a perl script that determines how many apache processes are running, when it gets near the max processes limit just restart apache. The trouble is, if you have other stuff going on with your sites (eg online ordering) your users will get a bit annoyed if you suddenly do a restart.
Cheers
|