We have 16GB total, but are only using 8GB (according to mysql and our dbadmin).

Kevin

On 12/8/06, joce@presence-pc.com <joce@presence-pc.com> 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.mesdiscussions.net
>
> > On 12/7/06, David Sparks <dave@ca.sophos.com> 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 sudden lock up and we are forced to restart mysql.
> >>
> >> That isn't a crash.
> >>
> >> Can you still connect to the db? If so output of 'show full
> >> processlist\G', etc would be useful.
> >
> >
> > Sorry, I shouldn't have worded it as a crash. Basically what happens
> > is that queries start stacking up and if we don't start killing
> > queries, we have to restart mysql before it crashes/restarts itself.
> >
> > We have spotted a couple of queries that we think might be causing the
> > problems, but even after adjusting the queries and the tables
> > (converting from InnoDB to MyISAM) we're still seeing the spike in
> > queries (not due to actual load).
> >
> > Here are links to our my.cnf and the output of "show innodb status" and of
> > "show variables":
> >
> > http://kold.homelinux.com/bj/my.cnf
> > http://kold.homelinux.com/bj/innodbstatus.txt
> > http://kold.homelinux.com/bj/mysqlstats.txt
> >
> > Maybe some of our settings could be causing the problem.
> >
> > Thanks for any help,
> > Kevin
> > --
> > Kevin Old
> > kevinold@gmail.com
> >
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe: http://lists.mysql.com/mysql?unsub=joc@presence-pc.com
> >
> >
>
>


--
Kevin Old
kevinold@gmail.com