Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Has anyone here encountered such scenario before where and update statement took longer time to run when innodb_buffer_pool_size is bigger.

I've run a few tests using the same statements on around 2500 rows of data on a single table, here are the data that I manage to get.

innodb_buffer_pool_size = 16M Time taken for SQL to complete - 1 min 25 sec

innodb_buffer_pool_size = 1G Time taken for SQL to complete - 3 min 45 sec

innodb_buffer_pool_size = 2G Time taken for SQL to complete - 4 min 53 sec

I'm running MariaDB 5.5 on an AWS EC2 instance with m1.large size. Does anyone has any idea how could this happened?

share|improve this question
    
Is the increased buffer pool size causing your insurance to start using swap space? That would be my first suspicion. – Michael - sqlbot Apr 9 '14 at 12:19
    
My server has 7GB of RAM and has no other service running except for MariaDB. And I don't have any swap configured for this particular instance. – dctw Apr 10 '14 at 15:24

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.