forum.coppermine-gallery.net

Support => cpg1.4.x Support => Older/other versions => cpg1.4 miscellaneous => Topic started by: roniabirk on February 21, 2006, 05:36:29 pm

Title: User List timeout
Post by: roniabirk on February 21, 2006, 05:36:29 pm

usermgr.php is timing out for me now that I have 15+ pages of users. I guess that is the equivalent of 300+ users.

How can I adjust the SQL query to reduce the processing time so it won't timeout? I've changed the users per page variable to 10, and that didn't help. I thought about using "Select TOP" but I don't know that it will achieve what I want either. I'm not a database guru what-so-ever.  :P

Any thoughts? I searched, and it seems like no one has been talking about the user list not loading for a few versions now, so sorry for the new topic.

Title: Re: User List timeout
Post by: Nibbler on February 21, 2006, 06:27:39 pm

Please post a link to your site.

Title: Re: User List timeout
Post by: roniabirk on February 21, 2006, 06:28:52 pm

http://stripedwall.com/cpg/

It is registration required right now though. Do you need a login?

ETA: Hm, it seems to be taking a long time on my other site, which has about 12 pages of members. http://spy-caps.com. Also registration required. Both hosted at Dreamhost on different servers though. I haven't had problems w/ timeouts with anything else lately.

Title: Re: User List timeout
Post by: Nibbler on February 21, 2006, 06:34:53 pm

By the looks of it you are the only/principle uploader of pics. If this is the case then check http://forum.coppermine-gallery.net/index.php?topic=27540.msg129081#msg129081

Title: Re: User List timeout
Post by: roniabirk on February 21, 2006, 07:19:18 pm

That does fix it. Why is that? I'm curious .. I guess without the index the query just takes longer, but why does forcing it help? Thanks!   :D

Title: Re: User List timeout
Post by: Nibbler on February 21, 2006, 08:01:55 pm

I think it wants to ignore the key since all the values of owner_id are the same. I don't get this issue in MySQL5 so presumably the optimizer has been improved/fixed.