|
|
Re: [CDO] Improve performance during loading [message #1426145 is a reply to message #1425459] |
Thu, 18 September 2014 10:01 |
Enrique Dela Messages: 3 Registered: September 2014 |
Junior Member |
|
|
Quote:This should execute nearly instant:
Code: [Select all] [Show/ hide]
CDOResource resource2 = transaction.getResource("model");
it's not instant and i don't understand why. Maybe i should add option on my reference. But in memory my object took 400Mo ... My Artifact is not an eProxy and i don't understand why
I'm reading the EMF Book and found this :
Quote:References can also be persisted across multiple resources (documents), where demand load and proxy resolution come into play.
Quote:Although, as we saw earlier, objects in containment references are implicitly included in their container's resource by default, it is also possible to enable cross resource containment. In Chapters 10
and 15 , we'll explore this topic, and look at demand loading, proxies, and proxy resolution in greater detail
Quote:The default EList implementation for containment references, used here, does not resolve proxies. This is because cross-resource containment support must be explicitly enabled for a model. This is done from within the EMF
generator, via a property on the root - level GenModel object. [9]The value of the "Containment Proxies" property determines whether any containment references in the model can be proxy resolving. If it is true, then any
EReference in the model for which resolveProxies is true will support cross-resource containment
I assume that i have to split my resource in CDO to optimize the loading.
[Updated on: Thu, 18 September 2014 13:04] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03385 seconds