I see several values set to '18446744073709551615', which is an
insanely large number for any memory setting (16.7 million terabytes
unless my math is wrong; huge in any case).
There was another person on the list earlier this year who had a
similar problem with large numbers, IIRC. I'd adjust t
Kevin Old wrote:
On 12/8/06, Philip Mather <[EMAIL PROTECTED]> wrote:
So something like 15G, that's not that bad. I'd run mtop as someone
suggested and see if some query is hammering it, maybe some other
process on the machine is hogging or going IO bound?
Thanks. We are watching the querie
On 12/8/06, Philip Mather <[EMAIL PROTECTED]> wrote:
So something like 15G, that's not that bad. I'd run mtop as someone suggested
and see if some query is hammering it, maybe some other process on the machine
is hogging or going IO bound?
Thanks. We are watching the queries. The pattern we
We have 16GB total, but are only using 8GB (according to mysql and our dbadmin).
Kevin
On 12/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
How much memory do you have on your system ? (the current setting in your
my.cnf could eat *a lot* of memory)
Thanks,
Jocelyn Fournier
www.me
[EMAIL PROTECTED] wrote:
Hi,
How much memory do you have on your system ? (the current setting in your
my.cnf could eat *a lot* of memory)
min_memory_needed = global_buffers + (thread_buffers * max_connections)
thread_buffers
---+-
sort_buffer_size
Hi,
How much memory do you have on your system ? (the current setting in your
my.cnf could eat *a lot* of memory)
Thanks,
Jocelyn Fournier
www.mesdiscussions.net
> On 12/7/06, David Sparks <[EMAIL PROTECTED]> wrote:
>> Kevin Old wrote:
>> > Hello everyone,
>> >
>> > We have a 4 CPU master se
On 12/7/06, David Sparks <[EMAIL PROTECTED]> wrote:
Kevin Old wrote:
> Hello everyone,
>
> We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
> MySQL with a mix of InnoDB and MyISAM tables.
>
> We normally run at 1500 queries/per second and lately, the server will
> all of a s
Kevin Old wrote:
> Hello everyone,
>
> We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
> MySQL with a mix of InnoDB and MyISAM tables.
>
> We normally run at 1500 queries/per second and lately, the server will
> all of a sudden lock up and we are forced to restart mysql.
T
No backups (like innodb-backup) running during these times.
We have 16GB of RAM and are currently using about 8GB of it.
We think we might have narrowed it down to a few hellish queries that
are hitting a few tables that we recently converted to InnoDB from
MyISAM. We're gonna convert them back
RAM too, how are you on RAM?
Obviously 100GB+ probably isn't going to fit in cache, but the usage pattern
during slower periods might be causing killer thrashing.
On Thu, Dec 07, 2006 at 12:43:17PM -0600, Dan Buettner wrote:
> Another thought is - do you have backups running during this time?
> S
Another thought is - do you have backups running during this time?
Something that might be attempting to backup live the InnoDB files?
We had similar problems with MySQL and backup software a while ago,
though we used all-MyISAM.
Dan
On 12/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
Hi,
Do you use MySQL with a NPTL or a linuxthread glibc configuration ?
Regards,
Jocelyn Fournier
www.mesdiscussions.net
> Hello everyone,
>
> We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
> MySQL with a mix of InnoDB and MyISAM tables.
>
> We normally run at 1500 qu
Hello everyone,
We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
MySQL with a mix of InnoDB and MyISAM tables.
We normally run at 1500 queries/per second and lately, the server will
all of a sudden lock up and we are forced to restart mysql.
This is not related to higher l
13 matches
Mail list logo
