mihaela wrote:Hi Robert,
I ran the same method that runs in the BP: in developer:
http://screencast.com/t/4npnQ3YpSince I did nothing in developer after running the method, looks to me that after a while, the memory is released..
I was wonderring if something like this can be triggered in the BP?
i see the line of the memory jump completely down (yes after you point this is the end but that is of no relation to when java gc does its job)
Its not then when a method/function ends that all resources are released right away, the gc is only doing some incremental quick stuff
When you look further you see that it hits the top line (i guess that 250MB) and then it really does a full gc and releases pretty much everything.
But looking at these memory usage tables doesn't say much about memory leaks, then you really have to know when also full gc's happens and over time you slowly see even with full gc's the min used memory creeping up.
Setting that client property makes no sense, it runs in the server, so it uses what you give the server. Is that really 250MB? thats a bit low for a server.. And thats why the cpu does a lot of stuff when i guess your batch jobs run
because it is really doing a log of Garbage Collecting because it is so tied in memory..