Skip navigation links

MySQL Forums :: Performance :: how mysql process resident memory is dependent on buffer pool size


Advanced Search

how mysql process resident memory is dependent on buffer pool size
Posted by: vivek d r ()
Date: October 05, 2012 03:53AM

in one of my server buffer pool size is set to 6GB. when i dump high end data on the database, say 2gb data, the mysql resident memory usage shoots up to 8GB which can be seen in "TOP" command. but after completion of this data insertion even after hrs of waiting, the resident memory usage doesnt drop down. it will be stuck at 8GB.. however now if i reduce the buffer pool size from 6GB to 2 gb the resident memory drops down.. this is not the best practise... is there any solution how to de allocate this resident memory after the completion of mysql processes?? and also what is the relation between this memory and buffer pool size... any help will be deeply appreciated.. thanks

regards
vivek

Options: ReplyQuote


Subject Views Written By Posted
how mysql process resident memory is dependent on buffer pool size 1409 vivek d r 10/05/2012 03:53AM
Re: how mysql process resident memory is dependent on buffer pool size 617 Rick James 10/06/2012 12:14AM
Re: how mysql process resident memory is dependent on buffer pool size 563 vivek d r 10/09/2012 04:17AM
Re: how mysql process resident memory is dependent on buffer pool size 578 Rick James 10/09/2012 11:46PM
Re: how mysql process resident memory is dependent on buffer pool size 540 vivek d r 10/11/2012 01:06AM
Re: how mysql process resident memory is dependent on buffer pool size 511 Rick James 10/11/2012 10:35PM
Re: how mysql process resident memory is dependent on buffer pool size 479 vivek d r 10/12/2012 12:07AM
Re: how mysql process resident memory is dependent on buffer pool size 484 Aftab Khan 10/19/2012 09:45AM


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.