[listadmin: majordomo was a little aggressive on filtering out possible
un$ub requests. sorry]
>Date: Tue, 22 Sep 1998 09:29:17 -0500 (CDT)
>From: Todd Michael Greer <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject: Re: RAMDISK for linux?
>
>On Mon, 21 Sep 1998, Jack wrote:
>
>> From: "Kurt D. Bollacker" <[EMAIL PROTECTED]>
>
>> I'm going to go nuts. Without rewriting tons of code, I need to speed my
>> simulations up my moving file accesses to a ramdisk. However, The linux
>> HOWTO's only talk about setting up small ramdisks for the booting process.
>> When I create a 128MB ramdisk using that procedure, the kernel becomes
>> un$table. Yuk! Any suggestions? Has anybody done this?
>
>As Linux caches disk accesses, ramdisks are not very useful. Instead,
>just be sure that you have sufficient free RAM available for the files to
>stay in RAM cache, and be sure that you pre-read all files that you need.
>When you read them this first time, they will be loaded into memory, where
>they will stay unless forced out by a shortness of RAM.
>Just 'cat file0 file1 file2 etc > /dev/null', then run your simulation.
>If you output a file, you don't need to cat it though, because it will
>already be in cache.
>
>If you _do_ set up a ramdisk, I think Linux is still liable to page files
>from the ramdisk out to disk. If, on the other hand, I'm wrong about
>that, and your cached files are getting paged out, (though they shouldn't
>be) then maybe a ramdisk would be a good option. I don't think it would
>be, though.
>
>HTH,
>Todd Greer <[EMAIL PROTECTED]>
>
>
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
