This doesn't make much sense for the RH system to
be that much faster than the SUSE system. There are
a few things that do come to mind when I think about
this:

1) GLIBC Version on RH and SUSE
2) Is mysqld stripped?
3) Are the same compile options used?
4) Kernel Version

Usually, Linux systems are no different than one another
except by what software is installed on a base install.
RH w/GlibC 2.2 and 2.4.X kernel will certianly be
faster than SUSE w/GlibC 2.1 and 2.2.X kernel.

As it would be faster than RH with 2.2.X kernel also.

I don't know, I would check kernel and glibc/libc versions.
And running background processes. If the suse system is running
X in the background, then it will be slower also.

Cheers.

---------------------
Johnny Withers
[EMAIL PROTECTED]
p. 601.853.0211
c. 601.209.4985 

-----Original Message-----
From: Jatin Nansi [mailto:[EMAIL PROTECTED]] 
Sent: Saturday, January 19, 2002 7:19 AM
To: [EMAIL PROTECTED]
Subject: Suse V/S Redhat - mysql performance difference.


Hi list,

I have 2 servers 1 running redhat 7.2 and the other running suse 7.3.
the hardware config is :

RH7.2: Fast desktop (IDE HDD/128 MB memory PIII 550 MHz).
Suse 7.3: Low end server (Ultra SCSI 2, PIII 850 MHz, 256 MB RAM).

Now i expect to see the suse server go faster than RH, but i am 
having the reverse happening. The RH server returns a query about
5 times faster.

For eg:
on RH:
------------------------------------------------------------------------
----
mysql> select straight_join docm.document_id, docm.document_title, 
docm.document_date, sources.source_name, cliptypes.cliptype,
byline.byline 
from keywords, documents_7 as docm use index (PRIMARY), dockeys_7 as
dock, 
sources, cliptypes, byline where keywords.keyword_id=dock.keyword_id and

docm.document_id=dock.document_id and docm.document_source_id = 
sources.source_id and docm.document_cliptype_id = cliptypes.cliptype_id
and 
docm.document_byline_id = byline.byline_id and (
keywords.keyword="assam" ) 
order by docm.document_id;

 <Lots of results>

|      219401 | WRONG POLICIES ARE THE BANE OF ASSAM

| 2000-08-21    | THE HINDUSTAN TIMES (DELHI)                    | N. A.
| 
PARASHAR, UTPAL        |
+-------------+---------------------------------------------------------
-----+---------------+------------------------------------------------+-
---------+------------------------+
276 rows in set (2.78 sec)

same query on suse:

 <Lots of results>

|      219401 | WRONG POLICIES ARE THE BANE OF ASSAM

| 2000-08-21    | THE HINDUSTAN TIMES (DELHI)                    | N. A.
| 
PARASHAR, UTPAL        |
+-------------+---------------------------------------------------------
-----+---------------+------------------------------------------------+-
---------+------------------------+
276 rows in set (7.06 sec)

This happens for all queries.
Of course the data is the same on both systems. The mysqld is what comes
with the distrib. (RH - mysql-3.23.22-6 / Suse - mysql-3.23.41-17).
I did try to use the official binaries from mysql.com but, i get the
same 
results on both systems.
I will probably install Redhat on the suse system, but can anyone
think of why this happens and what can i do to improve the response.
As of now the rowcount for the largest table is 221165.
Has anyone else noticed similar results?

Thanks for any replies 

Jatin

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail
<[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to