This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
See the URL: http://www.netbeans.org/servlets/UserList This is the only URL offered from an admin's start page. Probably in usability testing of SourceCast with dummy data, this seemed fine. Try it with netbeans.org, though, with apparently thousands of users. The page loads crawlingly slowly (over a minute) - presumably because it is searching the database for thousands of users, alphabetizing them, and showing you the first twenty or so. This is useless and annoying. Perhaps if my site has <50 users I would want to see them listed as is. But more than that, and there is little purpose in seeing them all listed. Furthermore, when I just want to look up a *particular* user, I first have to wait for the intro page to load, wasting a couple of minutes that I could have been working. In fact once you filter the list to show only users of interest, then the page loads perfectly fine. Normally this is done with a POST request, but I found that a GET request works just as well: http://www.netbeans.org/servlets/UserList?SIMPLE+FILTER+VALUE=joanne Such a direct query is what I almost always want when I click this link. I suggest that the "Administer Users" link first take you to a page where you are given a simple "filter" form that you can submit to go to the filtered user list. A different link would take you to the full unfiltered user list - and a warning next to the link would say "Warning: may be very slow". For UI comparison, see e.g. http://www.netbeans.org/issues/editcomponents.cgi?component=xml specifically the link at the bottom of the page: "Redisplay table with issue counts (slower)" which is a nice touch - lets you pay for the extra calculation if you really wanted it.
Action Plan: I'll look into this. Next update: Within 1 week. Thanks, Kristen
Update: Logged an issue with Engineering, PCN 13190. Action Plan: Waiting for more information from Engineering. Next Update: Within 2 week. Thanks, Kristen
Hi Jesse, Update: while our management considering this request I'm happy to say that at the next upgrade you can get to the users list much faster. Instead of around 1 minute you'll get the list in 6 seconds. This part of the code was already rewritten in new versions. I tested this on a client side which has also >5000 users. action plan: monitor internal issue for updates next update: Monday 12/16
Hi Jesse, update: our immediate plan is to give you a patch to 'make PeerBackedList.java faster and less memory-intensive. Instead of reading an entire list into memory, it reads only the number of entries neccessary to display a particular page of the list.' The above is from the README file for the patch which is already prepared. Action plan: i'll arrange a downtime of 5 minutes to put this patch on the site. Need this because the patch involves sandbox restart. I will coordinate with Jack about the timing when I got the OK from our engineers. Next update: tomorrow
Update: we hit a roadblock with the patch. It might have undesirable side effects as testing showed on stage. Action plan: monitor testing in internal issue. next update: tomorrow
update: our engineers are running more tests on the patch now. action plan:i'll monitor internal issue - pcn 13190 for updates. next update: on Monday 1/6/03
Hi Jesse, We have an update: patch was installed to improve access to user's list. My test shows it takes about 8-9 sec now. Also, the audit log comes up much faster (it was well over a minute in the past) as well. action plan: waiting for confirmation next update; upon confirmation
8-9 sec for a page load when there are thousands of users sounds tolerable enough - thanks.
Thanks Jesse, closing this.
UserList page now loads in less than 8 seconds and we also have a filter. The proposed enhancement as stated has not been fixed but since the performance has significantly improved, the issue has been addressed. As the reporter has agreed to the fix I am marking this as verified.
We recently moved out from Collabnet's infrastructure