Bugzilla – Bug 877857
Folder load time increases if default column order is modified
Last modified: 2015-01-15 22:47:28 UTC
This is an outcome of this discussion: https://teaming.innerweb.novell.com/ssf/a/c/p_name/ss_forum/p_action/1/action/view_permalink/entityType/folderEntry/entryId/691519/vibeonprem_url/1 It appears that if the default column order is modified, the folder load time can go from 2 seconds to 8-10 seconds. For example, move the 'Date' column to second place in a Discussion folder (Folder >> Folder Options >> Configure Columns >> Move Date to second place) Customer has over 20,000 entries in this folder and 8-10 seconds load time is too much for them.
Khurram, is the same problem as 877879? In that report the customer found that their security checker was eating lots of time and that they had some bogus stuff in their SSQRTZ tables. Clearing up those things fixed most of the problem.
(In reply to Peter Hurley from comment #2) > Khurram, is the same problem as 877879? In that report the customer found > that their security checker was eating lots of time and that they had some > bogus stuff in their SSQRTZ tables. Clearing up those things fixed most of > the problem. Yes, it is - after doing what they did in https://bugzilla.novell.com/show_bug.cgi?id=877879#c9, the overall load time went down to 3-5 seconds. It does not seem like more work is needed for this bug.
CCB: I believe this will have been fixed by the new GWT based folders.
In response to comment#8: In a discussion folder, on the far right of the folder menu bar (the one inside the view with New, Share, Delete, ...) there's a "cog" icon. Click that and select "Edit Column Layout" from the options presented.
Please go to bug #877879 to get the entry definition used by the USCG. Install this entry definition and enable it in a discussion folder. Then you will be able to add 100's of folder columns to try to dup the issue.
Marked Resolved/Fixed based on the previous comments. I'm assuming between the testing Ismael and Khurram have done with this, the the new GWT folder implementation fixed the problem.