[QUOTE]
Originally posted by Freiluft
[B]
Quote:
Originally posted by Joakim Agren
You missinterpretted my suggestion.I suggested that he/she should have increased the preffered memory(maximum) and not the minimum value.You should never increase the minimum value only the maximum value.And Apple recommends that you assign 30000-32000K of maximum memory to MRJ and minimum 40000K(But preferrably 64000) to LimeWire.
Sorry, Joakim, but you have misunderstood me. The default for LW is minimum: 1101 KB, preferred and recommended: 2125 KB. And you are saying what a wonderful world it would be to give LW 64000K??????? This might have been a good idea back in the days of memory leaks, but now it is really quite excessive. If an error happens when you give LW 5 or 10 MB, then it will happen if you give it that much as well. And if by chance one really does need to give LW complete control of your computer in such a way, then it is a very poorly written app.
Your Mac will not explode if you increase the minimum RAM allocated, or set minimum as the same as preferred/rec. I don't know where you get your information. I've been doing it for years to assure various apps. lots of breathing room (Word, for example), and as I recall, this was even a suggestion for Word. |
Hello!
Yes you are correct.I forgot for a moment that LimeWire is a Java App and behaves differently from ordinary apps.You do not have to allocate memory to LW it is one of the very few apps on a Mac that does that on its own just like apps do in Windows(But ofcourse it is limited by MRJ settings).I have given memory allocation advices so often when it comes to trouble shooting on the Apple Discussion Boards where I am a member for the past 3 years that it almost has become a reflex response.
However what is important is that enough memory is assigned to MRJ it should have a minimum of 30000K as the maximum value but there is no need to touch the minimum setting(and also you need minimum 64MB of free available Physical RAM to run Java Apps effectively and stable on Mac OS 9.1X and also VM turned off).
My experience with increasing the minimum settings is that it increases instability on computers with little RAM.I will use Internet Explorer 5.1.4 as an example.
I have assigned 46600k as the maximum value and left the default minimum value to 11792K.
This means that when I start IE up it will grab a chunk of RAM with the size of 46600(Even if IE tends to allow itself to go over that value slightly when heavily used).But it will start up by using only 11792K as breathing room but the more you use IE and the heavier sites you visit the more memory will be eaten up and eventually you will exceed the minimum value and start eating up on the rest of the breathing room that I have allowed for that app(but as I said IE is one of those apps that even goes over that value a little bit before crashing).This means that If I increase the minimum setting the rest of the breathing room becomes less and I also have to allocate the equivalent amount of more memory in the maximum setting.If I just leaves the minimum setting alone then I can do with less total RAM for that App.
To check how large memory chunks that every open app are currently using on your computer go here:
Apple Menu>About This Macintosh
Then when that window is open then go to the Help Menu and select Show Balloons.Now move your mouse cursor over each app and you will see the breathing Room that each and every app are currently using and hence the amount of memory left of each chunk allocated to each app.
But if you have little RAM 128MB or less and wants to use apps where stability is extermly important such as word processors Word etc then you should run it as a stand alone application with VM turned on and increase both the minimum setting upwards with 50% and the maximum setting with about 100%.So for those types of apps and with not very much RAM then adjusting the minimum setting is adviceable.
And no no Mac will explode when assigning more memory in the minimum setting
10.9.8.7.6.5.4.3.2.1.BOOM