[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Nss-mysql-devel] [ 101504 ] id command VERY slow
From: |
nobody |
Subject: |
[Nss-mysql-devel] [ 101504 ] id command VERY slow |
Date: |
Thu, 09 Jan 2003 04:42:11 -0500 |
Support Request #101504, was updated on 2002-Nov-07 22:26
You can respond by visiting:
http://savannah.nongnu.org/support/?func=detailsupport&support_id=101504&group_id=443
Category: None
Status: Open
Priority: 5
Summary: id command VERY slow
By: gmorin
Date: 2003-Jan-09 10:42
Logged In: YES
user_id=230
Browser: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226
Debian/1.2.1-9
This can be done with multiple selects. But my tests showed
that it was slightly faster with only one request. I guess
my tables weren't big enough.
In a perfect world, one request should be faster that three
requests but looks like we're far from that :-) I wonder if
this is fixed in MySQL 4.
Anyway, I'll change that in 3 selects.
Guillaume.
----------------------------------------------------------------------
By: kveton
Date: 2003-Jan-09 05:39
Logged In: YES
user_id=14541
Browser: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207
Phoenix/0.5
Let me guess, your tables are getting larger? It appears
nss-mysql uses 2 left joins which are just murder for MySQL.
The following is our query we've seen: select
site.unixname,500+site.id,"x",user.username from site LEFT
JOIN authors on site.id=500+authors.sid LEFT JOIN user on
authors.uid=user.id and 1=1 where 1 = 1 and 1=1
Phew!!
Any reason this can't be done with multiple selects? 3
selects would be better than this.
----------------------------------------------------------------------
You can respond by visiting:
http://savannah.nongnu.org/support/?func=detailsupport&support_id=101504&group_id=443