[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: Mon, 09 Dec 2002 14:54:07 -0500

Support Request #101504, was updated on 2002-Nov-07 16:26
You can respond by visiting: 

Category: None
Status: Open
Priority: 5
Summary: id command VERY slow

By: marcus
Date: 2002-Dec-09 14:54
Logged In: NO 
Browser: Mozilla/4.0 (compatible; MSIE 5.15; Mac_PowerPC)

Hi Guillaume

I did try nscd briefly, but the result of the id command 
was so slow on the first attempt (before nscd had had 
chance to cache the information), I abandoned this 
approach very quickly. Also, it would not be practical for 
me to configure it to cache user information for more 
than a few minutes, and since the system in question 
makes occassional use of many thousands of users 
(rather than frequent use of a few users), I don't think 
the effect would have been very significant.

Since our last communication, I have modified the 
system so there is now a group for every user. This has 
effectively solved the problem.

I realise now that the inefficiency is caused by nss 
rather than nss-mysql, but there is clearly an issue 
here that affects nss-mysql users. Perhaps it would be 
worth drawing this to the attention of the nss api 
developers. In the meantime, how about bundling 
some documentation with the nss-mysql distribution 
on how to maximise system speed and efficiency?

Sorry I can't contribute to the project myself - I'm only a 
lowly web developer/linux administrator!

Kindest regards



By: gmorin
Date: 2002-Dec-06 08:40
Logged In: YES 
Browser: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021128 

Hi Marcus,

Actually I would like to know if using nscd really speeds
things up, could try it for 10 minutes and tell if you see a
big difference. Furthermore, MySQL provides a way to log
slow queries, could you try it to see if there are no
queries realted to MySQL in it ? (see
for more details).



You can respond by visiting: 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]