Modifying Garbage Collection to increase performance
Rs as you well know is an application written in the Java programming language.
(the latest info I have, runetek is built on Java 6, but that might be outdated)
First, a little background info to explain what I'm doing:
Java is a garbage collected language, which is supposed to make life easier for the programmer. Non-garbage collected languages (for the most part, you could argue Objective-C is an exception and other languages that use allocate by reference counting, but I digress) require the programmer to manually determine how the application handles its RAM usage.
Periodically, the JVM that Java Applications run on top of will check to see if certain parts of the program are being unused at the time, and will remove those parts from memory. The default garbage collector in Java works serially, which means that the application itself is paused while the objects are cycled out of memory. In Java, garbage collection happens at non-predictable times, it is impossible to force the program to garbage collect.
So what does this mean?
Java has provided 2 different Garbage collectors besides the default that are designed to improve application performance by working in parallel with the application, and a required pause in the application is either extremely short, or will not happen very often, if at all.
=This concludes the wall of text=Close RS before you make these modifications, you will not be able to save otherwise.For Browser
Adding the Parallel GC method requires you to go to Control Panel/System Preference and locate the Java panel, click on it and navigate to the Java tab
Enter the following line into 'Runtime Parameters' -XX:+UseParNewGC
It should look like this:For Client
The way to modify the GC for RS is by editing the runescape.prm file in notepad or w/e text editor you use.
This file can be found in C:\Users\YourUsername\jagexcache\jagexlauncher\runescape
I believe the .prm extension is hidden by default, edit the file titled 'runescape'.
Delete the line labeled -XX:+UseConcMarkSweepGC and save
Door lag should be less significant, grey screen/black screen should also occur less frequently.
If this does not help you, let me know.
This works because two garbage collection methods are assigned to Rs, which seems to be a very dumb thing and is not recommended by Oracle. According to my test subjects, -XX:+UseParNewGC provides the greatest boost in performance. If you find the opposite is true, please provide the specs of your computer for research purposes.
If you want to learn more about Garbage Collection in Java + Performance tuning, here are some fine resources from Oracle (The company that owns Java):http://www.oracle.com/webfolder/technetwork/tutorials/obe/java/gc01/index.htmlhttp://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523.htmlhttp://www.oracle.com/technetwork/java/gc-tuning-5-138395.html