percona-discussion team mailing list archive

[Peter Zaitsev <pz@xxxxxxxxxxx>]

MARK, Vadim,

This  bug is about using glibc memory copy instead of "optimized" functions which
may be no more optimized.

I think this is generally true for a lot of stuff.

Regarding  checksums  yes...  checksum  is slow. Generally a lot of IO
path is too slow to be useful for SSD though this is the problem for a
lot  of  things  starting from RAID firmware - it is just not designed
for  devices handling 10K ops/sec which is about 2 orders of magnitude
faster than hard drives.

Tuesday, April 28, 2009, 5:58:24 AM, you wrote:

> Have you seen this bug report?
> http://bugs.mysql.com/bug.php?id=19975

> Also, have you done any experiments with the page checksum method for
> InnoDB to make it faster or to change the algorithm and I realize that
> changing the algorithm has a huge impact on deployed servers. Once you
> begin doing a lot of IO on fast SSD systems, you will burn a lot of
> CPU time doing checksum validation.




-- 
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501    Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911
Attend the 2009 Percona Performance Conf
Apr 22-23 http://conferences.percona.com/