[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Nss-mysql-devel] getent
From: |
Jelmer Vernooij |
Subject: |
[Nss-mysql-devel] getent |
Date: |
Mon, 13 May 2002 19:33:32 +0200 |
User-agent: |
Mutt/1.3.28i |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Now that I have finally abandoned my own nss mysql module, because it
was not thread safe, I noticed that this one is noticably slower for
getents.
It seems that first, a list with users is retrieved using
SELECT user.uid FROM user (or alike) and then a query to get the data
of a single user /for each user/. I have about 2000 people in my MySQL
table and one can imagine that this slows programs like 'finger' down
noticably.
Are there any reasons to do SELECT user.uid FROM user and then per
user queries? In my nss_mysql module, I just do
'SELECT user.uid,user.username,user.gecos,user.shell,etc FROM user',
which seems to work pretty fine (and faster).
Apart from that, keep up the good work !
Jelmer
- --
Jelmer Vernooij <address@hidden> - http://nl.linux.org/~jelmer/
Development And Underdevelopment: http://library.thinkquest.org/C0110231/
19:28:53 up 5:55, 8 users, load average: 3.59, 3.52, 3.28
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE83/jsPa9Uoh7vUnYRAkoyAKCW5rdLbwJLM/UVJgc5tQC29MErOQCcDjrK
96P8Imnx7tsX6EhQHCmEaxw=
=9luT
-----END PGP SIGNATURE-----
- [Nss-mysql-devel] getent,
Jelmer Vernooij <=