Thread View: comp.sys.next.software
1 messages
1 total messages
Started by Charles William Swiger
Mon, 09 Nov 1992 01:20
Re: nbuf=64/128 theory
Author: Charles William Swiger
Date: Mon, 09 Nov 1992 01:20
Date: Mon, 09 Nov 1992 01:20
32 lines
2020 bytes
2020 bytes
Excerpts from netnews.comp.sys.next.software: 8-Nov-92 nbuf=64/128 theory by L. Anathea Brooks@wam.um > I've changed my boot params using nbuf=128 or rather > nbu=128 because of 12 character limit. > > Now, I know this will speed up long compilations, perhaps > various sorts of number crunching. BUT is there any advantage > or speed gain in workaday world? I notice none, and wonder if > the memory used by the buffer might be better used as just > plain old memory. This seems to reduce the amount of drive access done under 3.0 quite noticably. It will help during any complex file access activity, such as compiling, using a database, navigating the filesystem with a browser, etc. This will also greatly speed up the floppy drive, once the disk pages have been loaded into memory. What you are doing is increasing the amount of paging activity slightly in order to considerably improve the disk caching performance of the filesystem. You may not need to have nbuf set that high is you don't do a lot of compiles. As a general rule, try setting nbuf equal to 5% of your real memory. For you that would be around 96. -Chuck +---------------------------------------------+ | Charles William Swiger -- CMU sucks rocks | "The television screen is the | AMS & normal mail: cs4w+@andrew.cmu.edu | retina of the mind's eye." | NeXTmail: <temporarily out of order> | +---------------------------------------------+ --Videodrome
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads