From: Heikki Tuuri (Heikki.Tuuriinnodb.com)
Date: Wed Jan 12 2005 - 03:17:25 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Brian,

unfortuntately, to use AWE/PAE in the InnoDB buffer pool you have to compile
MySQL yourself. See /mysql/innobase/os/os0proc.c. The reason is that the
MySQL official binary is built using an older version of MS Visual C++.

Then you could also lower the default 1 MB that Windows allocates as the
stack of each thread.

Best regards,

Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php

----- Original Message -----
From: <brian.ladishcpiqpc.com>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, January 12, 2005 5:20 AM
Subject: MySQL Memory Issue

> ------_=_NextPart_001_01C4F854.7050C7A0
> Content-Type: text/plain
>
> Windows 2000 Advance Server (latest service pack)
> Physical Address Extension enabled
> Dual 2.4Ghz Intel Pentium 4 Xeon
> 6gb of memory
>
> This system is running as a dedicated MySQL 4.0.12-max-nt server.
>
> Issue: The problem first exhibited itself as a connection issue. We
> weren't able to obtain more than 250 active connections. After
> troubleshooting we found that lowering the innodb_buffer_pool_size
> variable
> increased the number of available active connections. The
> innodb_buffer_pool_size was originally set at 1500M. Further
> investigation
> has determined that MySQL isn't able to use more than 2gb of memory on
> this
> system. It is our understanding that with PAE(Physical Address Extension)
> enables on the system that MySQL should be able utilize more than 2gb of
> memory. To prove that we were having problems with the 2gb memory limit
> we
> increased the innodb_buffer_pool_size to 2500M. At that time the MySQL
> service wouldn't start.
>
> We currently have the innodb_buffer_pool_size set to 1000M which is giving
> us the possibility of having about 650 active connections in MySQL.
>
> Does anyone have any suggestions as to what would be causing the memory
> limitation in MySQL?
>
> -Brian
>
> ------_=_NextPart_001_01C4F854.7050C7A0--

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]