Can't remember off the top of my head, I'll throw 5.x onto a lab box here in
a bit and see.
-Shawn
-Original Message-
From: Daniel Gerzo [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 25, 2005 2:59 PM
To: Shawn Mitchell
Cc: 'Michael Vince'; 'Steve Roome'; [EMAIL PROTECTED]
Subject: Re[2
On Saturday 25 June 2005 11:06, Michael Vince wrote:
> configuration file You will more then double your performance if
> you just start off by copying /usr/local/share/mysql/my-large.cnf
you are very fast with your conclusions ...
I am not a system engineer but
IMO it is not as easy as you sa
Nemam dobru naladu Shawn,
Saturday, June 25, 2005, 7:26:22 PM, si odoslal:
> I tested a MySQL install on a Dell 6600. It's specs were 8 GB ram, 12 x 73
> 15k rpm drives (Ultra320) on a RAID5, 4 Xeon MP w/ 2 meg of cache, HT
> enabled so the OS saw 8 CPU's.
> Every time, a stock linux install (S
I tested a MySQL install on a Dell 6600. It's specs were 8 GB ram, 12 x 73
15k rpm drives (Ultra320) on a RAID5, 4 Xeon MP w/ 2 meg of cache, HT
enabled so the OS saw 8 CPU's.
Every time, a stock linux install (SuSE, CentOS, and Fedora) were always
faster than FreeBSD stock, or custom kernel util
Your posting a lot of configuration here except the most easily
important one for performance in MySQL, thats your my.cnf configuration file
You will more then double your performance if you just start off by copying
/usr/local/share/mysql/my-large.cnf
to
/var/db/mysql
MySQL out of the box setup
From: "Arkadi Shishlov" <[EMAIL PROTECTED]>
Whats about performance and stability with MTU > 1500? I tried increasing
MTU on my Intel-made servers to speed-up NFS, but both 5.3 em and 2.x
Intel
provided drivers get stuck after some time with interface in OACTIVE
state.
The same happened to us
