RAM disk.
Masataka Ohta
mohta at necom830.cc.titech.ac.jp
Mon Oct 15 13:56:51 AEST 1990
In article <1990Oct11.185949.29164 at iconsys.uucp>
malc at iconsys.uucp (Malcolm Weir) writes:
>OK, Reach For Your Revolver... Make My Day! But you dudes who say "RAM disks?
>Unnecessary, 'cos we've got a Buffer Cache!!" are WRONG, INCORRECT, MISTAKEN,
>and basically WAY OUT OF LINE.
Not so much.
>Really? just how do you persuade *nix to cache "/lib/*", in prefence to
>Joe Unimportant-User's huge statistical jobs that have been munging vast
>amounts of data for the past 12 days?
As /lib is almost readonly, I recommend you to tune BSD file system
parameters such as maxcontig with appropriate disk controllers.
Then, you can read entire /lib/libc.a with a single seek.
>How do you persuade it that the
>disk accesses caused by the backup of "/irrelevant" are less important than
>the accesses caused by the CEO's secretary's WP temp files?
CEO's secretary should have his own workstation, of course.
>(btw, I used to be anti-RAM-disk, 'till I tried a system with "/lib"
> on RAM. "/tmp" didn't make that much difference, but you should've
> seen "ld" fly... )
If you are using your own workstation with large memory and dynamic
buffer caching, you can observe the same thing.
Masataka Ohta
More information about the Comp.unix.internals
mailing list