Community
Participate
Working Groups
When you access the Infocenter which including big index file, it takes a lot of time to load master index view. I think it's a performance problem.
Created attachment 47509 [details] Here is the sample index file You can reproduct the performance issue with this package.
Created attachment 52623 [details] Plug-in vresion of the zip file. Here is the plug-in version of the zip file that was originally provided.
The main performance issue that we are seeing in the master index view is that processing of the index file are in the main event queue and it's freezing the browser until processing of the index files is completed. The behaviour that we would like to see if something similar to the Search Index tab - some sort of progress indication, allow users to do other tasks while the indexes are being processed and the imaster ndexes cached (in alphabetical order) so that the master indexes is not sorted every single time it is started in standalone mode. In Infocenter mode, once the master index has been generated, it seems to be doing a better job loading the values into the view. But it seems to be using the event queue to load things and the browser is locked until all the index processing was completed. We have a workaround, where we can merge all the index entries into one large index.xml file, but that break our guidelines for creating documentation plugins. I'm using a WinXP Sp2 on a dual core 2.1Ghz machine with 2GB of RAM and it was taking between 1-2 minutes to process the indexes. Kind regards, Eric
As confirmed with Eric, it appears this performance problem has mostly gone away in 3.3 with the rewrite of the index loading code (from 1-2 min down to ~5s). Still, I am leaving open for more performance work near the end of 3.3.
Eric, can you comment on whether the problem you reported is now solved (or at least significantly improved).
Hi Chris, Preamble...I haven't tested the latest build. The last time I looked at this was a couple of weeks ago. For the issue of the Index Tab locking up the browser when loading the index entries. That has been solved. That was our main issue. The loading of the index has improved as well. I would say that the changes are significant. I do have a few more comments regarding this version of the index tab. - Visual queue for progress indication Is it possible to have something that displays a percentage of the time left to load the index entries. Something along the lines as the Search Index progress indication. - I can't tab to next and back links in the Index tab. - I haven't been able to test the Index Tab in infocenter mode yet, but only as help from the workbench. I'm not sure if the behaviour will be different in infocenter mode, but when I close the workbench and re-opne it later the help has to process the index entries again. If I open and close the help multiple times when the workbench is running, the Index Tab does not have to do any processing. Is it possible to have the same behaviour in the help when closing the workbench..with the caveat the if there were new plugins added, it's perfectly acceptable to process the indexes again. If these comments are best addressed as separate defects, please let me know. Eric
Chris, did you want to close this one?
Do I need to open a defect for the other issues that I had found/raised? Eric
Hi Eric, If you can file a new bug report for the other issue that would be great, then I'll close this one.
I think that between Curtis and myself we fixed this in M6. Eric can you file new bugs for any other performance problems (other than the problem already reported in Bug 178445).
Closing as fixed.
