[
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 ?
|
On 11/14/2013, 8:54, Martin Kočí wrote:
> Some common examples of problems that could cause excess path creation:
> - traversals of the resource tree. There is a heavily optimized
IResourceProxyVisitor class that will only instantiate Path object
lazily when requested, which can make a huge difference. Of course
minimizing/avoiding deep traversals altogether is even better.
> Resource changes occurring outside of builds or other batching
operations, which triggers excess resource change events
Yes, this is the case of maven from command line / in background +
refresh : this is the performance problem with m2e/maven builds.
For the record, m2e is not expected to modify workspace resources
outside of workspace build. If you see this happens, please open a bug
against m2e and provide small standalone example project and exact steps
to reproduce the problem.
--
Regards,
Igor