[eluser]Eric Brown[/eluser]
Thanks for the reply. Here's some more info in case it helps.
- How many hits per day, hits per hour at peak?
QPS under load is 24. Trying to plan for 100QPS
- What is causing the slow down? The database or the frontend?
The front-end, application logic is causing the spike in CPU usage. I don't know why yet.
- Look at mysql’s slow query log, does anything stand out?
I will look this. The thing is, I'm just doing Inserts with the only difference being what data is being inserted...I mean, it's just one table.
- How much file system usage does your app create? Do you have a lot of uploads/downloads?
Not sure what you mean by this. The table itself is about 2 million records right now and growing. About a gig of storage space.
- What kind of PHP memory usage execution times are you seeing for page loads
5 megs of memory is what the profiler says. Should I be looking somewhere else?
- Do you have any caching in place?
I have my lookups store in Memcache. Since I'm just writing to a db, there really isn't anything to cache. It's simply a web logging app that returns a 1x1 pixel.
