jwolfe Posted April 4, 2014 Report Share Posted April 4, 2014 We are hosting revive on Amazon Web Services. There are three web servers behind a load balancer all using the same RDS MySQL database. According to the database metrics, the server usually averages less than 20 connections at any instant. Then all of a sudden the number of DB connections are maxed out. Running SHOW FULL PROCESSLIST reveals that they are all running similar INSERT/UPDATE statements. INSERT INTO rv_data_bkt_m (interval_start, creative_id, zone_id, count) VALUES ('2014-04-04 23:00:00', '90', '14', '1') ON DUPLICATE KEY UPDATE count = count + 1 The server instance has been increased several times. It currently maxes out around 3,000 DB connections. It seems ridiculous to keep scaling up at this point. Is there an easy way around this? The only option I have right now is to hack into the core code. I'm thinking about using memcache or flat log files and updating rv_data_bkt_m in a batch mode. Any other ideas? Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.