Since version 2303 there has been a simpler way to view recent memory usage, go to Tools->Options->Startup & Shutdown and hit the button labeled 'JVM memory usage history' A line is written to the current file every 10 seconds detailing the most active thread along with the current memory usage. If you want to understand what memory is actually required then join the beta program (see the Help menu) and then observe the contents of the two log files 'thread_1.log' and 'thread_2.log' (usage is rotated) in the "logs" folder in the BiglyBT configuration folder. This means that often the JVM will use a significant amount of this due to lax garbage collection. Garbage collection takes time and effort so if the JVM has plenty of free heap memory it is somewhat lazy and allows the garbage to build up.īiglyBT sets the JVM memory limit to around 250MB to cater for a wide range of usage scenarios. ![]() Periodically the JVM runs 'garbage collection' cycles of varying degrees of aggressiveness, searching for and freeing objects that are no longer needed. ![]() The JVM is configured with a maximum amount of memory that it is allowed to use when allocating objects, the 'heap'. ![]() BiglyBT runs within the Java garbage collected virtual machine (JVM).
0 Comments
Leave a Reply. |