Bug 159756 - Allow modules to bundle preindexed data
Allow modules to bundle preindexed data
Status: NEW
Product: editor
Classification: Unclassified
Component: Parsing & Indexing
6.x
All All
: P2 (vote)
: TBD
Assigned To: Tomas Zezula
issues@editor
indexing
: PERFORMANCE
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-06 09:22 UTC by Erno Mononen
Modified: 2010-08-20 09:12 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erno Mononen 2009-03-06 09:22:09 UTC
Filing for tracking purposes as discussed in the meeting. May or may not be a stopper for migrating Ruby to CSL, we 
need to do some performance measurements to find that out.
Comment 1 Vitezslav Stejskal 2009-03-10 15:52:37 UTC
This is a deficiency in the indexing infrastructure. As discussed, modules should have a possibility to preindex
libraries and bundle the index data in the IDE installation. When the IDE is installed the preindexed data will be used
instead of indexing the same libraries again. This is purely a performance improvement.
Comment 2 Vitezslav Stejskal 2009-04-08 20:27:07 UTC
Considering the high number of other high priority issues related to the indexing infrastructure I've just asked for
permission to defer this issue to the next release.
Comment 3 John Jullion-ceccarelli 2009-06-02 15:57:59 UTC
Would expect this of all JARs we ship with the IDE, plus major platforms (GF/Java SE/Ruby) etc.
Comment 4 David Strupl 2009-06-02 16:02:36 UTC
When speaking about java: according to Dusan rt.jar (main component of JSE) index is about 3 MB and we could save approx
10 seconds of scanning during the first startup of the IDE. I am not sure it is worth bundling those 3 MB but if we find
out that e.g. glassfish jars for web projects would make the initial experience of developing web app better we might
consider it for the glassfish jars. Petr?
Comment 5 Petr Jiricka 2009-06-02 16:13:01 UTC
Yes, I think that's a possibility worth looking at.
Comment 6 Vladimir Voskresensky 2009-06-02 16:19:53 UTC
Just an idea:
why don't you integrate this process into installer phase, instead of increasing download side?

Thanks,
Vladimir.
Comment 7 Tomas Zezula 2009-06-30 18:03:42 UTC
The easiest way is to allow modules to provide lucene index which is then copied (extracted) to the ${nbuser}/var/cache/index/**/ folder.
Tor already had this feature in the GSF, probably can be taken from there.
Comment 8 Tomas Zezula 2009-06-30 18:06:03 UTC
The lucene index was designed to be relocated (it does not contain any absolute path, holds for both parsing.api and java index).
So it's safe to copy it or to connect it to the sources located on other absolute URI.
Comment 9 Vitezslav Stejskal 2010-01-15 05:30:18 UTC
We have been living without prebundled indices for several releases now and have had no really strong complaints about it.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo