Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 Jul 2006 12:42:14 -0300
From:      Vinicius Vianna <ds@hacked.com.br>
To:        Thaddeus Quintin <thaddeus@dm1.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Memory usage for MySQL
Message-ID:  <44C398D6.60007@hacked.com.br>
In-Reply-To: <407487AA-A1C4-4581-A7EA-2FBC68E284C6@dm1.net>
References:  <407487AA-A1C4-4581-A7EA-2FBC68E284C6@dm1.net>

next in thread | previous in thread | raw e-mail | index | archive | help
 From what I read you should only change kern.maxdsiz, changing 
kern.dfldsiz makes every process allocating this amount of memory by 
default, thats bad.

Something like:

kern.maxdsiz="1395864371" # 1.3GB
#kern.dfldsiz="1395864371" # 1.3GB
#kern.maxssiz="134217728" # 128MB

would do the trick for you, check limits also and see what the init 
scripts may be limiting on this process.

HTH,
DS

Thaddeus Quintin wrote:
> I'm working on a FreeBSD 6.1 machine and setting up MySQL 5.0 with 
> some InnoDB tables.
>
> The machine has 2GB of RAM and will primarily be used as a database 
> machine and will also be serving files over NFS (not high volume).
>
> The issue that I'm having is that when I start up MySQL I get a couple 
> "Out of Memory" errors before it actually starts up.  Looks like this-
>
> 060719 11:55:35  InnoDB: Started; log sequence number 0 43656
> /usr/local/libexec/mysqld: Out of memory (Needed 950109184 bytes)
> /usr/local/libexec/mysqld: Out of memory (Needed 712581120 bytes)
> 060719 11:55:35 [Note] /usr/local/libexec/mysqld: ready for connections.
> Version: '5.0.22-log'  socket: '/tmp/mysql.sock'  port: 3306
>
> If I reduce or increase the innodb_buffer_pool_size variable for MySQL 
> I can eliminate or increase the number of errors.  This set of errors 
> was with innodb_buffer_pool_size set to 600M
>
> This is what top currently shows for MySQL-
>   PID USERNAME  THR PRI NICE   SIZE    RES STATE  C   TIME   WCPU COMMAND
>   871 mysql       8  20    0  1196M   159M kserel 0   0:01  0.00% mysqld
>
> I tweaked /boot/loader.conf to allow larger data size for processes 
> already (rebooted after changes)-
> kern.maxdsiz="1395864371" # 1.3GB
> kern.dfldsiz="1395864371" # 1.3GB
> kern.maxssiz="134217728" # 128MB
>
> If there's an out of memory error, how come MySQL starts up?  Is this 
> something to be concerned about?  What else should I be checking to 
> figure this out?
>
> Thanks-
> Thaddeus
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44C398D6.60007>