|
If the DB were overwhelmed with queries you'd see general site slowness - what I saw instead was page requests would either return quickly or hang for extended periods of time. That tells me queries werent making it to the DB either because not enough processes (or threads if you're using threading) were available on the web server to answer user request or on the DB server to answer web server requests (assuming web server -> DB.) That's a memory issue. Either the server doesn't have enough memory or it does and the max number of processes/threads isn't set high enough to take full advantage of existing memory. A faster drive will help because queries will be processed more quickly, freeing up processes/threads more quickly, but unless the server is tuned to balance memory usage w/DB capability you're leaving performance on the table.
Thanks either way. Can't be fun fixing a problem you're not seeing. The other possibility is its a network issue and requests are limited before they reach the web server which is why you're not seeing it. But the problem was intermittent enough that an average user might not.
|