Re^2: RAM disk.

Chris Old chris at ctk1.UUCP
Wed Oct 17 18:39:48 AEST 1990


mohta at necom830.cc.titech.ac.jp (Masataka Ohta) writes:

>In article <1990Oct11.185949.29164 at iconsys.uucp>
>	malc at iconsys.uucp (Malcolm Weir) writes:

>>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.

Can you do this on Sys5?

>>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.

Get real.

>>(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.

What a silly remark. We are not talking about how we can speed up
things by throwing money at them, we are talking about how we can
improve performance of an _existing_ configuration.

--------------------
Chris Old (C.t.K.)            | ddsw1!olsa99!ctk1!chris
Tran Systems Ltd              | olsa99!ctk1!chris at ddsw1.mcs.com
If you have no reason for your opinion, change it.



More information about the Comp.unix.internals mailing list