Re: MySQL optimisation for single laptop with 16 GB RAM
Posted by:
Rick James
Date: September 10, 2016 12:17AM
Your two changes are probably good.
Although the buffer_pool could be higher, you probably need to leave a lot of RAM for R.
"bigger isn't always better" -- very true.
Some JOINs are quite performant; some are terrible. I can't make a useful statement without further info.
join_buffer_size and tmp_buffer_size should not be bigger than 1% of RAM.
Many performance issues are due to a missing 'composite' index.
Subject
Views
Written By
Posted
1790
September 08, 2016 05:58AM
Re: MySQL optimisation for single laptop with 16 GB RAM
1000
September 10, 2016 12:17AM
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.