Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-core-dev] The new JDTindex. Should I note a difference as user?

Do you expect the new implementation to be faster when indexing large workspaces (thousands or projects with gigabytes of dependency jars)?

Oh -- you should see a decent speed improvement when opening the type hierarchy in large workspaces. No other speed improvements are expected in this version.

On Tue, Oct 11, 2016 at 6:40 PM Stefan Xenos <sxenos@xxxxxxxxxx> wrote:
No. The new index is not intended to speed up indexing time. It will eventually speed up all searches and most operations that read from .class or .jar files. It also makes the index fully readable during indexing which will potentially allow us to make some things that currently block on the indexer become nonblocking.

In the current (incomplete) implementation, indexing time is expected to take about twice as long since the old indexer is still active and there are now two indexers competing for resources.


On Tue, Oct 11, 2016 at 6:04 PM Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
Do you expect the new implementation to be faster when indexing large workspaces (thousands or projects with gigabytes of dependency jars)?

--
Regards,
Igor


On Tue, Oct 11, 2016, at 08:58 PM, Stefan Xenos wrote:
You shouldn't notice a difference as a user. If nothing is broken then this version is working correctly. I had to disable the cache changes to get the tests working, and without the cache changes the performance improvements are fairly modest.

The index hasn't been adopted in search or open type yet. We've only adopted it in the type hierarchy. You should see a slight performance improvement in the type hierarchy, but we'll need to finish the work on the JavaModelManager cache and do more adoption before we see more widespread improvements.

  - Stefan

On Tue, Oct 11, 2016 at 12:15 PM Lars Vogel <lars.vogel@xxxxxxxxxxx> wrote:
Hi,

I'm trying to test the new index from Stefan. Is there anything I
should note as a user?

JDT search operations performance feels the same to me.

For example creating the index for > 2000 classes in Open Type seems
still be at similar speed. I'm not sure how to test the index
creation, I usually activate and deactive the "Include all plug-ins
from the target platform in Java search" PDE preference.

Best regards, Lars

--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com
_______________________________________________
jdt-core-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
_______________________________________________
jdt-core-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev

Back to the top