At 12:23 + 3/26/04, Tim Cutts wrote:
Tim:
Can you bring your libc to the latest patch level?
Not necessary. I resolved the problem:
binlog_cache_size was set to 32MB
I didn't realise that this would automatically be allocated to every
thread, even if there are no InnoDB or BDB tables in th
Tim:
Can you bring your libc to the latest patch level?
Not necessary. I resolved the problem:
binlog_cache_size was set to 32MB
I didn't realise that this would automatically be allocated to every
thread, even if there are no InnoDB or BDB tables in the entire
instance. This explains why --
Tim Cutts wrote:
On 25 Mar 2004, at 10:10, Tim Cutts wrote:
No, indeed. I'm going to try building mysql myself, on the machine on
which it's going to be running, and see whether that still has the
issue...
The version compiled natively on the machine does the same thing
(although it uses a li
On 25 Mar 2004, at 10:10, Tim Cutts wrote:
No, indeed. I'm going to try building mysql myself, on the machine on
which it's going to be running, and see whether that still has the
issue...
The version compiled natively on the machine does the same thing
(although it uses a little less memory
On 25 Mar 2004, at 06:31, Heikki Tuuri wrote:
you can use the command
SHOW INNODB STATUS;
to check how much memory InnoDB has allocated in total. Please report
what
it says at the time of the memory explosion.
Well, that was informative, but in a negative sort of way. SHOW INNODB
STATUS produ
On 25 Mar 2004, at 05:01, Sasha Pachev wrote:
Innodb to my knowledge does not allocate very much locally per thread,
and should not allocate anything at all if you are not doing any
queries.
That's what I thought.
Based on the test results you have reported, I would put your libc as
the primary
Tim,
- Original Message -
From: "Sasha Pachev" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, March 25, 2004 7:04 AM
Subject: Re: Mystifying mysqld memory usage explosion
> Tim Cutts wrote:
> >
> > On 22 Mar 2004, at 18:24, Tim
Tim Cutts wrote:
On 22 Mar 2004, at 18:24, Tim Cutts wrote:
Some users' code is causing MySQL's memory use to explode. By the
time we reach about 200 simultaneous connections, the MySQL server is
using 8GB of virtual memory, and then falls over (the machine is an
AlphaServer ES45 with 8 GB of
I'm not a big mysql expert but I think mysql has some buffers which it
keeps per connection
here are some examples (from mysql website):
/
/If you have complex queries |sort_buffer_size| and |tmp_table_size| are
likely to be very important. Values will depend on the query complexity
and availab
On 22 Mar 2004, at 18:24, Tim Cutts wrote:
Some users' code is causing MySQL's memory use to explode. By the
time we reach about 200 simultaneous connections, the MySQL server is
using 8GB of virtual memory, and then falls over (the machine is an
AlphaServer ES45 with 8 GB of physical memory,
Some users' code is causing MySQL's memory use to explode. By the time
we reach about 200 simultaneous connections, the MySQL server is using
8GB of virtual memory, and then falls over (the machine is an
AlphaServer ES45 with 8 GB of physical memory, and 16 GB of swap,
although processes are c
11 matches
Mail list logo
