Heavy IOPS and database use
-
I like the concept of this cache, and decided to try it on our production servers last night during somewhat modest traffic.
APCu was caching correctly, at least according to the APCu status page showing hits/misses and memory usage. We were getting about 3500 requests/sec on the APCu cache on each of our two web servers.
CPU usage on our two web servers did go up by about 25-30%, which I suppose makes sense given how this works.
However, the load on our MySQL database skyrocketed and we ran in to unusable limitations with maxed out IOPS, high database CPU usage and ultimately maxing out our PHP-FPM pool when it spawned more and more processes.
I guess I can provision more IOPS on our DB server and try again, but any guidance here? The improved performance over memcached or redis might come at the expense of having to trick out the database server to support this style of caching.
- The topic ‘Heavy IOPS and database use’ is closed to new replies.