----- Original Message -----
From: "Ken Kirchner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 10, 2001 2:35 AM
Subject: Re: [OT] RE: RAMdisk to improve map change performance?? Ithink not


>
> On Tue, 9 Oct 2001, Stan Hoeppner wrote:
>
> > This might be worth the money for a niche small dedicated app that
doesn't
> > generate much data, but for HLDS files?  My CS dir is 384MB alone!  Any
idea
> > what size RAMdisk you'd need to put all the HLDS files in it?  Would you
> > store your log files there as well?  If not, you've got some surgery to
> > perform on your HLDS config, in order to write out to your physical disk
ban
> > file and logs in REALTIME.  If your server goes down (the machine, not
> > HLDS), bye bye ban file, logs, etc.
> >
> > Suffice it to say, trying to use a RAMdisk to host the files for an HLDS
> > server is a crappy idea.
>
> Well.. trying to use THAT ramdisk might not fly, but I think Quantum makes
> something called an SSD (Solid State Drives or such) which is exactly as
> it sounds.  A hardrive made up of memory chips.  Ungodly performance
> compared to your normal spinning disk type media.  Of course, they are
> expensive as hell! :)  Oh and they werent very big.  I think last I saw
> they were around 1GB max, but it's been awhile.  Cant imagine what a RAID
> set-up with these puppies would be like.  I think the limitations of
> current drive controllers would be the bottleneck.
>
> What you need for the PC is something like the Amiga's RAD device. It was
> a RAM drive that was recoverable after a reboot (usually).  One of the
> many neat tricks the Amiga was able to pull of back in the 80's.
>
> But other than the intial map loading, there isnt a whole lot of disk I/O
> on an hlds server is there (assuming your arent swapping)?
>
>
> --
> Ken Kirchner                    :  [EMAIL PROTECTED]
> Assistant System Administrator  :  Tel (318)222-2638
> ShreveNet, Inc.                 :  Fax (318)213-2650
>
> ShreveNet - Your Premium Internet Service Provider!
>
>
>


Reply via email to