Printable View
Hi
I have a Java application which i call in a loop and put the same Sring randomally
to a method and the application write this to system out.
Wenn I call this program in a loop 200000 times I see that the memory increases in JVM which is not usual I think. Is there a way to give memory free each time when a loop round (1,2,3,4....) is ended??
regards
Not. Java can't manage memory. You just are tuning garbage collector or you can use other OOP, which can manage memory for example C/C++.
can I tune and call GC in running loop?how?Quote:
Originally Posted by Petr
There is no need to fiddle with the garbage collector; as long as there is more available memory the gc doesn't do anything, i.e. a new object can be allocated from the available memory. When the jvm runs out of memory the garbage collector fires up and frees (all) unused memory. What you're seeing is normal behaviour. You can set the maximum available heap memory with the -Xmx flag. Better stay away from the garbage collector, it doesn't need any help.Quote:
Originally Posted by henry123
kind regards,
Jos
Yep.
The JVM will often use up memory up to xMx. You've offered it xMx memory so it (not unreasonably) thinks it may as well use it. Then it does a gc.
If you follow it on a graph it's like a heart beat.
you say this is a normal behavior, but I have several JAVA applications runing as a batch program (in a loop doing something whole time) and their meory size stay during the execution almost the same. Ok, some of them increase a smal portion memory use, but other increase nothing!. How do we explain that? Apart from that I did observe my applicattion mentioned in my first posting, it increases after one hour almost double memory size :D . Is not that risky, that somewhen a stack overflow ocurs?Quote:
Originally Posted by JosAH
Regards
The question is, why do you need to free the memory?
You've givent he JVM a certain amount of memory to work with, so what's wrong with it using that?
If, as time goes by, the amount available after a garbage collection is shrinking then you might have a problem, but otherwise it's really nothing to worry about.
Ok, I understand that it is a normal behaviour in JAVA(in other programing languages maybe is not normal) this is now not more my question.Quote:
Originally Posted by Tolls
But the question ist now, how can I understand it, ths same Program does the same test on the same data (conditions are 100% the same and this is not multi threading application) nevertheless increases the memory size continuesly!
Consider that in a round in a loop, the same program begins and ends and I expect tha the GC begins to clear the heap, each time a loop round ends, where is the GC in this case?
The gc happens whenever the GC decides it needs to. This has nothing to do with your loop at all. It is, by and large, out of your hands.
I try to be more clear, let change the question as follow, if the same application (meaning same code with the same input and output data) is called in a loop 1000 times and creats each time f.i 100 objects which are the same objects in each loop, there will exist 1000 x 100 Objects at the end of the loop still in heap? If so it means the old objects in heap (created by this application in previous rounds ) will not be rewritten, but a new version of them are created in the heap?
No.
They could be collected sooner.
There's nothing to say that gc won't collect some of these objects before the loop has finished.Code:for (int i = 0; i < 1000; i++) {
Object o = new Object();
}
If it doesn't then yes, there will be 1000 objects which will all be eligible for garbage collection should it be required.
In the old days the garbage collector was simply a 'mark and sweep' algorithm: as long as more memory was available nothing was done; as soon as a single memory allocation failed the garbage collector marked all reachable chunks of memory, moved them over in memory and released all other memory (there was only garbage in it). This caused your program to stop temporarily while the garbage collector was doing its evil deeds.Quote:
Originally Posted by henry123
Nowadays the garbage collector tries to avoid this sudden temporay freeze of your program by running in a separate thread and doing a bit of clean up behind the scenes, i.e. some objects might be collected and others are left as garbage. This makes the behaviour of the garbage collector less predictable (to those that are/were used to the simple mark and sweep algorithm) but it most certainly does its job). Only after a full garbage collection not enough memory can be allocated an OutOfMemoryError is thrown. Trying to 'help' the garbage collector is just hindering it most of the time.
kind regards,
Jos
@Tals. JosAH
thanks, now the idea ist more and how the GC handlels data
Thanks, regards