[EMFStore] Performance Hit by number of checked out projects [message #1478994] |
Tue, 18 November 2014 23:39  |
Eclipse User |
|
|
|
We have about 20 projects in our EMFStore server and each project includes around 500k objects per project (relatively large projects).
Our users mostly like to checkout all the projects and have all of them in the workspace. However, what we noticed is that when the number of projects in the workspace increases, the commit and update time for a single project gets effected. I should add that none of these projects has any cross references to each other and they are completely separate.
Is this a known issue? Our profiling shows a linear increase in the commit/update time relative to the number projects in the workspace. We kept changins only a single attribute for all our tests. The I can also see in the CPU profiling that the eSet and eGet methos is getting called more times than the number of instances of the class in the single project.
I tried to get more tracking but I couldn't find more infor about what is the method that calls the eSet I just can see ESLocalProject.commit is calling esSet and eGet methods.
Another proof that I found was to have projects with models from different packages in the workspace. When I profile committing one project, I see calls the the eSet method of the package that doesn't exist in the committing project!
Please let me know if I can provide more data.
Thanks,
Roza
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.26881 seconds