Community
Participate
Working Groups
20040315 This may be the nature of the beast but I thought I would log a trace anyways. When I compiled all of SWT the Java Indexer took 55s to complete (the build took about 120s in comparison). STEPS 1) Turn off autobuild 2) Load swt and swt win32 3) rename classpath_win32 to classpath 4) Turn auto build on I will attach a trace
Created attachment 18836 [details] Trace of Java Indexer
Tod, the Java indexer has nothing to do with the Java builder. I suspect that the slow down you're seeing is due to the Java builder running at the same time. Can you please confirm this ?
Yes - if you look at the steps then you will see that the builder is running as I had just turned the auto build on.
I looked at the steps :-) But I'm missing the point of this bug report. Can you please rephrase the problem ?
I wanted to point out that the JavaIndexing took about half as long as building which seemed pretty long. If this is not an issue that close this report - I don't understand your domain well enough to say whether or not this should be flagged.
I think this is a natural consequence of multi-threading on single processor machine. Closing
Agreed - my suggestion was just that you try and defer the indexing to reduce the Thread count. Having said that as this is a non UI Thread that may not win us much if the context switching doesn't happen that often. My machine is dual processor BTW.
We reuse the same thread for all indexing activity, so no big deal.
