Hamish Spires is a SysOp in the Novell Support Forums, and wrote a wonderful little tool. You can get the details here:
http://www.novell.com/coolsolutions/tools/16991.html
This wonderful little thing will take the output of another cool tool called SEG:
http://www.novell.com/coolsolutions/tools/14445.html
And spit out memory tuning recommendations for your NetWare box. So long as the server has more than 2GB of RAM, though. If it at or under 2GB it doesn't spit any recommendations, and IMHO it kinda should. But still, very useful.
NetWare 6.5 Sp3 introduced a new way of managing memory in NetWare, and it has taken Novell a year to get it nominally right and it still needs work. From SP3 on one of the most frequently posted questions in the support forums have been of this kind:
"I'm getting cache-allocator errors, what do I do?"
And that's attributable, according to Hamish, to Novell picking the wrong thing to optimize memory for. He provides the hand tuning you can do to get those month long uptimes back. In my case the server.exe from SP5 helped a LOT. But these settings can be used to get the server's memory more stable. It'll also keep it from fragmenting nearly as bad as it would out of the box.
Perhaps SP6 will include the 'correct' tuning parameters.
Tags: novell, netware
http://www.novell.com/coolsolutions/tools/16991.html
This wonderful little thing will take the output of another cool tool called SEG:
http://www.novell.com/coolsolutions/tools/14445.html
And spit out memory tuning recommendations for your NetWare box. So long as the server has more than 2GB of RAM, though. If it at or under 2GB it doesn't spit any recommendations, and IMHO it kinda should. But still, very useful.
NetWare 6.5 Sp3 introduced a new way of managing memory in NetWare, and it has taken Novell a year to get it nominally right and it still needs work. From SP3 on one of the most frequently posted questions in the support forums have been of this kind:
"I'm getting cache-allocator errors, what do I do?"
And that's attributable, according to Hamish, to Novell picking the wrong thing to optimize memory for. He provides the hand tuning you can do to get those month long uptimes back. In my case the server.exe from SP5 helped a LOT. But these settings can be used to get the server's memory more stable. It'll also keep it from fragmenting nearly as bad as it would out of the box.
Perhaps SP6 will include the 'correct' tuning parameters.
Tags: novell, netware
you and buckys blog having a little copying going on huh? cool.anyways, too bad servers with <2gig dont benefit from this tweak
No, we just share a common passion on this topic :)I've since learned that if you throw in the -i parameter, you can tell memcalc that you have 2GB+1 memory, and it'll spit out recommendations.
now that is useful info!
With the exception of doing the DS preallocation, I haven't really seen any improvements from manually tunning servers at less than 2GB. The default settings seem to work okay. If you've got example servers where manual tuning has improved them, I'd be interested in seeing the segstats and config reports from them. Likewise any comments or suggestions on improving MemCalc welcomed. There is an NLM version in the works that will make all the changes automatically - save on the cut and pasting. If anyone wants to have a look at a preview version (it make the recomendations, but doesn't apply the changes yet), drop me a mail at hamish@haitch.net and I'll send it out.Hamish.