From owner-freebsd-questions Mon Apr 13 12:37:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01969 for freebsd-questions-outgoing; Mon, 13 Apr 1998 12:37:37 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from indigo.ie (nsmart@ts01-59.waterford.indigo.ie [194.125.139.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01901 for ; Mon, 13 Apr 1998 19:36:21 GMT (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id UAA07000; Mon, 13 Apr 1998 20:36:20 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199804131936.UAA07000@indigo.ie> Date: Mon, 13 Apr 1998 20:36:20 +0000 In-Reply-To: Geoffrey Robinson "Re: RAM Drive" (Apr 13, 3:02pm) Reply-To: rotel@indigo.ie X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: geoffr@globalserve.net, Dima Dorfman Subject: Re: RAM Drive Cc: questions@FreeBSD.ORG Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Apr 13, 3:02pm, Geoffrey Robinson wrote: } Subject: Re: RAM Drive > Thanks for the suggestion but that wouldn't help much since I want a RAM > drive for faster I/O. I've got CGIs that run up to 3 times a second and > each time they read in several big data files and make lots of changes > to them that have to be committed to disk each time. It is possible to > use RAM memory for a virtual drive and speed I/O access up, right? Well, if they have to be committed to disk, then a RAM drive isn't a good idea as the machine could fail at any time leaving the disk file out of sync. If you can get away with flushing to disk every 100 or so requests perhaps you could keep the data files in a SYSV shared memory area? I'm not sure if perl lets you do that kind of thing. -- Niall Smart. Microsoft Suck. See www.freebsd.org for details. echo "#define if(x) if(!(x))" >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message