MySQL Forums
Forum List  »  General

Re: MySQL Memory Usage to Caculate
Posted by: Rick James
Date: March 27, 2015 04:35PM

Long ago, I decided it was hopeless to try to compute the memory with a formula like that.

tmp_table_size is especially problematic -- A complex SELECT could allocate multiple tmp tables.

If you have "max_connection" connections actually running, you have bigger problems. That is, it is almost always ok for the computation to exceed how much RAM you have.

Most users _need_ to change innodb_buffer_pool_size to be about 70% of _available_ RAM, and not touch anything else.

Sometimes someone gets carried away -- thread_cache = 1000, query_cache_size = 1G, join_buffer = 1G, etc. It's a disaster.

Options: ReplyQuote


Subject
Written By
Posted
Re: MySQL Memory Usage to Caculate
March 27, 2015 04:35PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.