|
On Apr 25, 2013, at 11:20 AM, Paul Willis <paul.willis@me.com> =wrote:1) MySQL would dump the expired query cache for a query =that got a lot of requests (as it should the data had been updated and =the cache was old) but it took too long to process and a queue of the =same big query quickly built up from which it could not recover, just as =you describe.Interesting, =but how did you resolve this if it was indeed causing a =slowdown?
Another option which might =help (which we did) is to split the MySQL off onto it's own =serverPaulAlso =interesting, but if the problem was squarely on MYSQL, then I'm not sure =how having it separated would help all that much. Maybe free up a few =CPU ticks from apache.
The move to OSX was as =much about getting me into something I had more experience with =admittedly as anything =else.
I am intrigued though =that you were having similar issues.What =was your ultimate resolution? Did you find a bad query? Was it the cache =dump primarily? Or an overtaxed server?Chasing this thing has =been like chasing shadows. You think you got it and then 3 hrs later its =back.
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...