|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
2.93.230.145
In Reply to: RE: Yes, boot.ini is posted by riboge on December 05, 2011 at 08:52:53
You say cpu is working harder. Is it with /maxmemory or /burnmemory?
Follow Ups:
I reverted to maxmem as suggested. This time the cpu ran in the teens rather than low single digits I can't explain the change. Now maxmem runs just a few percent less cpu usage than burnmemory, and perhaps the latter sounds a bit better since now with our new math I am burning more memory to get a truer 256 remainder (3072-2716).
Please, if you have time and leasure, keep the record of these settings reverting from one to another and try to record the cpu usage. I wonder if both commands allow to bite off a different part of the physical memory every time, and it is important to catch the least possible, if it is possible at all.
Serge
(Certainly, if You have time to do it)
ALSO, Did You try yhe full line with /nopae and/onecpu settings?
What do you think of the sonic change?
Edits: 12/05/11 12/05/11
I have gone back and forth between maxmem and burnmemory three more times. I complicated it a bit by reducing the resulting memory used progressively. Still I never reproduced the very low cpu usage I saw at first. It must have been an anomaly or mistake of some kind. In all cases usage varied mostly in the range of 15-20% with spikes into the 20's. I have now gotten down to using 226MB with maxmem. It is hard to say there was any significant improvement in sq beyond the initial benefit of reducing to maxmem=256. If any it is refinement of ultra-refinement. I repeat that I have been using the full boot.ini line with /nopae and /onecpu all along with this.
It is puzzling to me given the overall goal of reducing cpu stress that this memory limitation improves things though increasing cpu usage--though it is now usage of one core instead of two. Contradicts our premise, doesn't it?
And it is something to think about.
Serge.
It is working harder with burnmemory by a factor of 5: 1-3% for maxmem vs up to 15%. These memory limitations should increase it some, yes? That is one reason I was questioning whether maxmem was really having an effect. Clearly burnmemory is re cpu work.
Decisively, /maxmemory should be used. And, btw. I am already hearing the roar of distant laughter at our common math. 1 Gb is 1024 mb (512+512)
Serge.
Obviously, we both have our minds on a higher plane...and what's a few dozen MBs one way or the other anyway.:) I am heading back to maxmem on the double.
Post a Followup:
FAQ |
Post a Message! |
Forgot Password? |
|
||||||||||||||
|
This post is made possible by the generous support of people like you and our sponsors: