Printable View
I've attached an image of the view I get:
The spike that you see in the first graph from around 70 to 120 is when I add call my function to add the file to mySQL. Ironically, it adds it fine using the profiler. But it doesn't work with the jar. I guess, its unable to allocate the required memory when I'm running the program via .jar? And maybe the Profiler is intelligent enough to allow it to do so?
Where did you read that?Quote:
Originally Posted by worldChanger
This is what the Sun Hotspot JVM FAQ says:
What are the default heap sizes for 64-bit VMs if GC ergonomics is not used?
The default heap size for all 32-bit J2SE implementations is 64MB. We have adjusted the defaults for 64-bit implementations to be 30% larger in order to make up for the increased size of Java objects due to larger native pointers. Remember that Java objects contain class and lock pointers so even if you create Java objects which contain only integers, each object takes up additional memory.
How large a heap can I create using a 64-bit VM?
On 64-bit VMs, you have 64 bits of addressability to work with resulting in a maximum Java heap size limited only by the amount of physical memory and swap space your system provides.
The maximum theoretical heap limit for the 32-bit JVM is 4G. Due to various additional constraints such as available swap, kernel address space usage, memory fragmentation, and VM overhead, in practice the limit can be much lower. On most modern 32-bit Windows systems the maximum heap size will range from 1.4G to 1.6G. On 32-bit Solaris kernels the address space is limited to 2G. On 64-bit operating systems running the 32-bit VM, the max heap size can be higher, approaching 4G on many Solaris systems.
Learning how to learn is life's most important skill...
T. Buzan