-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi bas,
You did not provide details on your harddisk in your message, you might want to know that
MySQL performance is highly related to your diskconfiguration. If you want to speed it up you could do a softwareraid 0 over as much disks that fit in your machine. And also consider disks with a good cache.
the sparcs are a litte different in case of harddisk's:
the V480 does have a veritas-fs-mountpoint with a symmetrix in background - i asume that is pretty fast, because it was originally focused on oracle.
the enterprise does have no raid's and really simple scsi-drives (a litte old you know ;-)
in comparison we have raid5 with scsi-disks and this cciss-compac-controller.
so you suggest that there is a huge point in harddisk.
i might have to run a view benchmark tests directly on the disks to see the thrououtput in reading data(-junks).
the only thing that bothers me is: why should the harddisk be such a big impact if i am using an index and _not_ selecting all data (in fact: the select brings only a view hundred rows up).
but i try to figure out if there is a difference in reading between the sparcs and the intel.
thanks for the hint mac
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi there,
hope this haven't been discussed in that kind of detail in older topics:
the facts in short: - - we have the same mysql-version (4.0.18) for an intel-machine and a sparc-machine. - - we have a table with about 5,500,000 rows - - we do a "realtivly" simple select on a varchar-50-field (with an index of course) - - the statement takes 4s on the intel- and 24s on the sparc-machine - - we played around with some caching-features on the sparc-side but there was no significant increase of speed
the hardware: sparc: Sun Fire V480 4 x UltraSPARC III Cu Processor 900 MHz 16GM RAM
intel: Compaq DL380R02 2 x Pentium III 1.1 GHz 4 GB RAM
the installation on the sparc was done with a precompiled version. the intel-one was compiled by our self (but no special configue-options).
we also ensured that the index on the sparc side is in good shape. we also tested it with the same setup on an older enterprise 450 - same bade timing.
if you need more detail i can deliver them. but i am more interested in a general question:
does the speed of mysql depends more on things like the processor than other resources? if so: what kind of general suggestions can be made about using select-statements on huge tables to be "fast" over different platforms?
i am also aware of the hints about not using to huge logtables for statistical output rather then creating small statistic tables. this is something we will do, but we also need sort of guidelines for future projects.
thanks in advance for your suggestions.
with regards mac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin)
iD8DBQFA5YJVvkHn/oGTPXURApvwAKDBBcLtRH+S1+tBLsrFNmimtSki+gCgkQA6 MEQxsqwYzRjQx+lN+epJtao= =2VNS -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin)
iD8DBQFA5r5jvkHn/oGTPXURAogvAJ9Vccf97+qCYiMesMYA/CV3q0zYAwCeOpiW zdYgBw/A9TrJATEZBx/yRzU= =E2Ck -----END PGP SIGNATURE-----
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
