[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-core-dev] [perf] org.eclipse.core.runtime.Path (computeSegments) : is cache possible ?
|
Hi,
I have more info about this problem.
1) My (test)cache in org.eclipse.core.runtime.Path.computeSegments retains ~ 250MB of (segments) String [] in my test case. I think this is a good trade off in this case : the ratio Memory/Cpu is good.
A question : in there in equinox / eclipse platform a generic concurrent cache implementation with timeouts etc .. ?
2) After the build are in heap many instances of org.eclipse.core.runtime.Path (~100 000, retain 400MB) : those references aren't from my test-cache for org.eclipse.core.runtime.Path, but from eclipse self. It means, something holds already references to org.eclipse.core.runtime.Path permanently : I`ll investigate it more.
3) URL : instances of java.util.URL are also ummutable like Path. The build creates also many, every time with same String-paths (the profiler marks the constructror of java.util.URL as hotspot)