Hi,
I made some Java and SQL optimization: * Indexes * Replace subquery by inner joins * Remove 1=1 from where ;) * Tweaks on H2ConnectionFactory
Now on large project in my test environment, h2cache is not required. For me, everything is faster, less memory usage.
Here is my experiment: https://github.com/zulus/dltk.core/commit/5be4dc62ffed6c19a431b91915c1b9010c7363bb
How I’m testing: - 2 large Symfony 2 projects in workspace
- Enable all highlighters
- Open 2k file with many nested call
- Format your file , next run CA
- Check your profiler ;)
Advantages: - faster eclipse startup !
- Open PHP type always working (without “wait for indexer”)
Before I send a patch to bugzilla, I have to perform some code cleanup. I also see two other points for optimization in h2 indexer.
-- Dawid Pakuła +48 795 996 064
The test I ran yesterday for only for importing huge
existing project in the workspace. There is a search operation for
each file before it is indexed (to avoid indexing the same file
twice). In this case the h2 cache is indeed an overhead because
most of the time the searched file isn't available neither in the
h2 cache, nor in the h2 db.
Today, I ran an additional test - I searched for a method
reference in this same huge project. Well, without the cache this
operation is 3 times slower. My system is with SSD. I guess that on
HDD it will be even more slower.
So, it's seems that the h2 cache really optimizes search
operations.
Kaloyan
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pdt-dev
|