Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » [CDO 0.8.0] Performance
|
Re: [CDO 0.8.0] Performance [message #122923 is a reply to message #122918] |
Fri, 23 May 2008 11:57 |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Simon,
Comments below.
Simon McDuff wrote:
> Hi Eike,
>
> In EMF, everythings is somehow attached from a resource.
> However, in our production system, our IStore never update objects
> Resources.
>
> Now, that I need to follow the standard, I developped my IStore to update
> every objects correctly. However, when we create thousands of objects and
> add it to the resource.contents... it starting to get very slow. Also it
> needs to go through the list to find out if we already have the items..
> etc..etc..
>
Maybe you want to create a root contain so the resource has one child
and that child has all the other contents. Then you can manage the list
of all objects in the store itself.
> Here my questions:
>
> Can we persist objects without adding it to the resource ?
>
In general, an object for which eResource() == null can't be persisted.
> Could we persist object in a way where objectA.resourceID == resourceA but
> resourceA.content will not contains objectA ?
> This is in Fact how the result of never updating a Resource.(My previous
> IStore)
>
> We could have something like.
> CDOTransaction.persist(CDOResource, object);
>
> Do you think it will go against something ?
>
Very likely. It's best to meet all the expectations of the framework...
> Thank you.
>
>
>
|
|
|
Re: [CDO 0.8.0] Performance [message #122935 is a reply to message #122923] |
Fri, 23 May 2008 12:19 |
Eclipse User |
|
|
|
Originally posted by: stepper.sympedia.de
Ed, Simon,
I agree with Ed.
I always recommended to handle the attachment of href'ed objects
explicitely so that it is clear where they're contained.
I believe most strategies to automatically attach referenced but
uncontained objects is not scalable in the best case.
And I only agreed to develop something like a CDOAutoAttacher because it
is completely optional.
Cheers
/Eike
Ed Merks schrieb:
> Simon,
>
> Comments below.
>
> Simon McDuff wrote:
>> Hi Eike,
>>
>> In EMF, everythings is somehow attached from a resource.
>> However, in our production system, our IStore never update objects
>> Resources.
>>
>> Now, that I need to follow the standard, I developped my IStore to
>> update every objects correctly. However, when we create thousands of
>> objects and add it to the resource.contents... it starting to get
>> very slow. Also it needs to go through the list to find out if we
>> already have the items.. etc..etc..
>>
> Maybe you want to create a root contain so the resource has one child
> and that child has all the other contents. Then you can manage the
> list of all objects in the store itself.
>> Here my questions:
>>
>> Can we persist objects without adding it to the resource ?
>>
> In general, an object for which eResource() == null can't be persisted.
>> Could we persist object in a way where objectA.resourceID ==
>> resourceA but resourceA.content will not contains objectA ?
>> This is in Fact how the result of never updating a Resource.(My
>> previous IStore)
>>
>> We could have something like.
>> CDOTransaction.persist(CDOResource, object);
>>
>> Do you think it will go against something ?
>>
> Very likely. It's best to meet all the expectations of the framework...
>> Thank you.
>>
>>
|
|
| |
Re: [CDO 0.8.0] Performance [message #618162 is a reply to message #122918] |
Fri, 23 May 2008 11:57 |
Ed Merks Messages: 33217 Registered: July 2009 |
Senior Member |
|
|
Simon,
Comments below.
Simon McDuff wrote:
> Hi Eike,
>
> In EMF, everythings is somehow attached from a resource.
> However, in our production system, our IStore never update objects
> Resources.
>
> Now, that I need to follow the standard, I developped my IStore to update
> every objects correctly. However, when we create thousands of objects and
> add it to the resource.contents... it starting to get very slow. Also it
> needs to go through the list to find out if we already have the items..
> etc..etc..
>
Maybe you want to create a root contain so the resource has one child
and that child has all the other contents. Then you can manage the list
of all objects in the store itself.
> Here my questions:
>
> Can we persist objects without adding it to the resource ?
>
In general, an object for which eResource() == null can't be persisted.
> Could we persist object in a way where objectA.resourceID == resourceA but
> resourceA.content will not contains objectA ?
> This is in Fact how the result of never updating a Resource.(My previous
> IStore)
>
> We could have something like.
> CDOTransaction.persist(CDOResource, object);
>
> Do you think it will go against something ?
>
Very likely. It's best to meet all the expectations of the framework...
> Thank you.
>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Re: [CDO 0.8.0] Performance [message #618165 is a reply to message #122923] |
Fri, 23 May 2008 12:19 |
|
Ed, Simon,
I agree with Ed.
I always recommended to handle the attachment of href'ed objects
explicitely so that it is clear where they're contained.
I believe most strategies to automatically attach referenced but
uncontained objects is not scalable in the best case.
And I only agreed to develop something like a CDOAutoAttacher because it
is completely optional.
Cheers
/Eike
Ed Merks schrieb:
> Simon,
>
> Comments below.
>
> Simon McDuff wrote:
>> Hi Eike,
>>
>> In EMF, everythings is somehow attached from a resource.
>> However, in our production system, our IStore never update objects
>> Resources.
>>
>> Now, that I need to follow the standard, I developped my IStore to
>> update every objects correctly. However, when we create thousands of
>> objects and add it to the resource.contents... it starting to get
>> very slow. Also it needs to go through the list to find out if we
>> already have the items.. etc..etc..
>>
> Maybe you want to create a root contain so the resource has one child
> and that child has all the other contents. Then you can manage the
> list of all objects in the store itself.
>> Here my questions:
>>
>> Can we persist objects without adding it to the resource ?
>>
> In general, an object for which eResource() == null can't be persisted.
>> Could we persist object in a way where objectA.resourceID ==
>> resourceA but resourceA.content will not contains objectA ?
>> This is in Fact how the result of never updating a Resource.(My
>> previous IStore)
>>
>> We could have something like.
>> CDOTransaction.persist(CDOResource, object);
>>
>> Do you think it will go against something ?
>>
> Very likely. It's best to meet all the expectations of the framework...
>> Thank you.
>>
>>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
| |
Goto Forum:
Current Time: Mon Sep 23 15:05:13 GMT 2024
Powered by FUDForum. Page generated in 0.04330 seconds
|