| Resource unload doenst free memory? [message #430920] |
Wed, 17 June 2009 13:51  |
Eclipse User |
|
|
|
Originally posted by: wesendon.in.tum.de
Hi,
I'm working with a big model, which is splitted in several resources.
I've written a cleaner thread, which unloads all unused resources (using
resouce.unload()). Still, all elements are in one big containment tree.
So unloading "proxyfies" these elements. But the problem is, that the
memory footprint doesn't drop? Is unload not ment for these kind of
issues, am I doing something wrong and is there another possibility?
Greetings,
Otto
|
|
|
| Re: Resource unload doenst free memory? [message #430921 is a reply to message #430920] |
Wed, 17 June 2009 14:02  |
| Eclipse User |
|
|
|
Otto,
Yes, in this regard EMF currently works as designed although this
knowledge is not too wide-spread. For this reason I blogged about the
internal details some while back. You might find this reading
interesting:
http://thegordian.blogspot.com/2008/11/how-scalable-are-my-m odels.html
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Otto schrieb:
> Hi,
>
> I'm working with a big model, which is splitted in several resources.
> I've written a cleaner thread, which unloads all unused resources (using
> resouce.unload()). Still, all elements are in one big containment tree.
> So unloading "proxyfies" these elements. But the problem is, that the
> memory footprint doesn't drop? Is unload not ment for these kind of
> issues, am I doing something wrong and is there another possibility?
>
> Greetings,
> Otto
>
|
|
|
| Re: Resource unload doenst free memory? [message #655213 is a reply to message #430921] |
Fri, 18 February 2011 11:42 |
| Eclipse User |
|
|
|
Hi Eike,
Thanks for the link, it is indeed a very interesting reading.
You mention that you have seen EStore implementations which maintain a separate store instance for all objects of a resource. Do you have more details about that approach.
Thanks & best regards!
|
|
|
Powered by
FUDForum. Page generated in 0.05027 seconds
Home