java using 200 MB of memory with only tws
- Thread starter Cdntrader
- Start date
Here's a really dumb question that I can't get answered by googling.
The Java version they call AMD64 Windows, does that refer to the 64 bit version of windows or what?
Since I have an AMD 64 cpu. but the 32 Bit XP Pro, this does create confusion.
I know the plain old window version will work fine, but wanted some clarification here.
The Java version they call AMD64 Windows, does that refer to the 64 bit version of windows or what?
Since I have an AMD 64 cpu. but the 32 Bit XP Pro, this does create confusion.
I know the plain old window version will work fine, but wanted some clarification here.
Thats correct. But next week you're going to be starting a new thread that TWS memory usage is growing to 512MB. I thought you were trying to reduce the memory footprint...
Thanks, skunk, for pointing that out.
If I recall correctly from studying Java's memory model a while back, "lazy programming" and "memory leaks" are generally not applicable to Java in the same way as C++. The nature of Java's model is that the programmer does not explicitly release memory as one does with free() and delete - rather that memory is automatically reclaimed by the garbage collector as needed and as defined by memory management params. Increasing -Xm lets the heap grow bigger until the GC has to run, which may increase performance by spending fewer resources on GC. Unless, of course, you are short of physical memory, in which case it will probably worsen things because the OS ends up having to use swapfile (on disk) to satisfy part of the memory allocation.
AFAIK, as long as the Total Commit Charge stays under Physical Memory (as shown in Task Manager), you're cool. If not, get more memory or reduce the value of -Xm by the amount it is exceeding it (assuming that it's Java, and not something else, that is sucking up a lot of memory).
If I recall correctly from studying Java's memory model a while back, "lazy programming" and "memory leaks" are generally not applicable to Java in the same way as C++. The nature of Java's model is that the programmer does not explicitly release memory as one does with free() and delete - rather that memory is automatically reclaimed by the garbage collector as needed and as defined by memory management params. Increasing -Xm lets the heap grow bigger until the GC has to run, which may increase performance by spending fewer resources on GC. Unless, of course, you are short of physical memory, in which case it will probably worsen things because the OS ends up having to use swapfile (on disk) to satisfy part of the memory allocation.
AFAIK, as long as the Total Commit Charge stays under Physical Memory (as shown in Task Manager), you're cool. If not, get more memory or reduce the value of -Xm by the amount it is exceeding it (assuming that it's Java, and not something else, that is sucking up a lot of memory).