Jeremy Zawodny wrote:
Now, I just have to remember to push out mytop 1.3 so that folks can
shake out any new bugs I've introduced...
Just make it one binary that recognizes its argv[0] calling (like gzip)
and also supports command-line options. The two data collection methods
are the same
> One of my favorite Borg quotes is: "Crude but effective." :-)
I like that. ;)
This got me thinking again about a feature I'd like to see in mysqld. I'd
like to add something like SQL_STATISTICS to SELECT/UPDATE/INSERT
statements. The idea would be that if this keyword was used, then mysqld
woul
On Wed, Jan 22, 2003 at 06:06:51PM -0800, Steven Roussey wrote:
> > Hmm. mytop 1.4 will have a feature that may help you
>
> 1.4? I'm still on 1.0. Guess I'm behind the curve.
Well, 1.3 is sitting in my CVS tree. I just need to update the docs
and changelog. I already have some patches pending
> Hmm. mytop 1.4 will have a feature that may help you
1.4? I'm still on 1.0. Guess I'm behind the curve. Jeremy, can you add
something to protect against binary data coming across in a query and
messing up the terminal window? Leave it running a while and all of a sudden
it is a big mess. Yikes!
On Wed, Jan 22, 2003 at 02:21:34PM -0500, Michael T. Babcock wrote:
> Steven Roussey wrote:
>
> >Might also look at:
> > vmstat 1
> >
> >
>
> `vmstat 1` is my favorite instant-info server debugging tool. I
> wouldn't mind the same program for MySQL (where's that mytop author
> anyhow? j/k)
Steven Roussey wrote:
Might also look at:
vmstat 1
`vmstat 1` is my favorite instant-info server debugging tool. I
wouldn't mind the same program for MySQL (where's that mytop author
anyhow? j/k)
Blocked processes (second column) is a very useful piece of info too.
--
Michael T. Babcoc
m: "Steven Roussey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "'Jeff Kilbride'" <[EMAIL PROTECTED]>
Sent: Wednesday, January 15, 2003 4:04 PM
Subject: Re: Optimizing Ext3 for MySQL
> I use ext3 and have a qps of anywhere from 2800-8000 and use t
I use ext3 and have a qps of anywhere from 2800-8000 and use the
defaults with no problems. Have you tried:
iostat -k 1
to look at your disk access? What kind of disks are they anyhow? IDE or
SCSI? RAIDed? In what fashion?
Lastly, you said that this is a script that is running, right? The tab
On Wed, Jan 15, 2003 at 11:24:05AM -0800, Jeff Kilbride wrote:
> >
> > By "updated" you mean inserts? Or are you doing a table scan for each
> > update (since they're not indexed)?
>
> No, they're actual updates (UPDATE table SET field=value WHERE
> primary_key=value2). The field being updated is
- Original Message -
From: "Jeremy Zawodny" <[EMAIL PROTECTED]>
To: "Jeff Kilbride" <[EMAIL PROTECTED]>
Cc: "MySQL" <[EMAIL PROTECTED]>
Sent: Wednesday, January 15, 2003 10:41 AM
Subject: Re: Optimizing Ext3 for MySQL
> On Tue, Ja
On Tue, Jan 14, 2003 at 11:33:54PM -0800, Jeff Kilbride wrote:
> Are there any general guidelines for optimizing ext3 for MySQL? I have a
> perl script that runs 200K + updates into my database once a day and I see
> pretty wildly fluctuating query/sec numbers using Jeremy Z's
Are there any general guidelines for optimizing ext3 for MySQL? I have a
perl script that runs 200K + updates into my database once a day and I see
pretty wildly fluctuating query/sec numbers using Jeremy Z's mytop program.
I've seen in excess of 2000 qps and then seen that number drop
12 matches
Mail list logo
