[THIN] Re: RAMDISK
- From: "Bernd Harzog" <Bernd.Harzog@xxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Mon, 16 Feb 2004 08:27:41 -0500
Good product, good people. What is does is allow you to replace part of =
your mechanical rotating magnetic disk storage with a solid state disk =
storage. So, you can put things like your page file (or part of it) on a =
drive that is much faster than an ordinary disk drive, and almost as =
fast as memory. Since you are not reducing the amount of RAM available =
to applications when you do this, this is not a case of robbing Peter to =
pay Paul. It is however, quite a bit more expensive, than for example =
our product TScale, which works by reducing the number of things that =
have to be kept in the page file.
Cheers,=20
Bernd Harzog
CEO
RTO Software, Inc.
bernd.harzog@xxxxxxxxxxx
678-455-5506 x701
www.rtosoft.com
-----Original Message-----
From: Steve Snyder [mailto:steven_snyder@xxxxxxxxx]=20
Sent: Sunday, February 15, 2004 11:21 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: RAMDISK
Or for those of you who recall Digital's non-voltile
ramdrives for VAXs, here's the modern equivalent (they
claim to increase a citrix box's scalabilty, so I'm
interested to read what Bernd thinks about it)
http://www.tigicorp.com/tigijet.htm
fwiw - I used to use ramdrives in the old days to
increase compiling performance until disk-caching
pretty much gave me the same advantage, which is why I
think its largely unused these days
--- Alexander Danilychev <teknica@xxxxxxxxxxx> wrote:
> Bernd is right -- 32-bit memory addressing allows
> access only 4 gigabytes of=20
> physical memory (2 GB for user addressable memory,
> unless you are on Windows=20
> 2003 when you can bump it to 3GB at OS expense).
> RAMDISK, as I understand,=20
> has access to kernel memory space.
>=20
> I am not sure, however, I share Bernd's concerns -
> techniques like "PAE x86"=20
> (this is where Joe's comment comes in) change the
> memory addressing from=20
> 32-bit addressing mode to 64-bit addressing mode
> (check interesting article=20
>
http://www.microsoft.com/technet/treeview/default.asp?url=3D/technet/prod=
technol/windowsserver2003/proddocs/techref/W2K3TR_pae_what.asp).
>=20
> In other words, even on 32-bit OS/hardware using
> RAMDISK sparingly should=20
> not create a problem.
>=20
> In any event, RAMDISK can be used to force specific
> apps, let say=20
> tracing/logging application, to run from RAMDISK and
> collect data there=20
> (temporarily of course). Otherwise we might have
> very little control=20
> regarding app data placement (memory versus disk) if
> we have no access to=20
> the source code.
>=20
> ALEX
>=20
>=20
> >From: "Joe Shonk" <joe@xxxxxxxxxxxxxxxxxxx>
> >Reply-To: thin@xxxxxxxxxxxxx
> >To: <thin@xxxxxxxxxxxxx>
> >Subject: [THIN] Re: RAMDISK
> >Date: Sun, 15 Feb 2004 10:29:41 -0700
> >
> >I'm not sure where you are getting that 4GB
> limitation.
> >
> >Windows 2000 Server and Windows Server 2003
> Standard supports 4GB Max.
> >Windows 2000 Advanced Server supports 8 GB Max
> >Windows Server 2003 Enterprise Edition supports 32
> GB Max (x86 Based
> >Processors) 64GB Max for the DataCenter Edition.
> (again x86 bases)
> >
> >HP has 2xway Xeon servers that support 16 GB of
> RAM, and 4xway Xeon servers
> >that support 32-64G of RAM.
> >
> >Joe
> >
> >-----Original Message-----
> >From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On=20
> >Behalf
> >Of Bernd Harzog
> >Sent: Sunday, February 15, 2004 7:29 AM
> >To: thin@xxxxxxxxxxxxx
> >Subject: [THIN] Re: RAMDISK
> >
> >I would be very interested in knowing if anyone has
> been able to use a =3D
> >RamDisk in terminal server environment to any great
> effect. Here my =3D
> >concern. You have 4GB of addressable memory in
> Windows NT/2000/2003 when =3D
> >running on 32 bit chips. Let's say you have 4GB of
> RAM on a server, and =3D
> >an 8GB page file (12 GB of virtual memory). If you
> take 512MG of RAM and =3D
> >make a RAM disk, you may cause the OS to take 512MB
> of stuff that was in =3D
> >RAM in put it on the page file. In other words you
> are simply robbing =3D
> >Peter to pay Paul with no net gain.
> >
> >If someone has results that are different than what
> I have outlined =3D
> >above, I would be very interested to hear about it
> >
> >Best Regards,
> >
> >Bernd Harzog
> >CEO
> >RTO Software, Inc.
> >bernd.harzog@xxxxxxxxxxx
> >678-455-5506 x701
> >www.rtosoft.com
> >
> > -----Original Message-----
> >From: Alexander Danilychev
> [mailto:teknica@xxxxxxxxxxx]=3D20
> >Sent: Sunday, February 15, 2004 12:06 AM
> >To: thin@xxxxxxxxxxxxx
> >Subject: [THIN] RAMDISK
> >
> >Run into an interesting site regarding RAMDISK.
> There might be =3D
> >interesting=3D20
> >uses for Citrix related applications:=3D20
> >http://home.tiscali.be/ir006712/RAMDisk/RAMDisk.htm
> >
> >Based on Microsoft RAMDisk sample (Q257405). Code
> for original "free"=3D20
> >version 1.0 is available here:
> >http://codeguru.earthweb.com/system/RAMDisk_src.zip
> >
> >Free version or $10 for "extended" version 2.2.
> >
> >Here is some info from the site:
> >"A RAMDisk acts as a virtual drive on your system.
> It allows you to =3D
> >create=3D20
> >directories, copy files to and from it, etc.... The
> data however is not=3D20
> >written onto a hard disk, but remains purely stored
> into a particular =3D
> >part=3D20
> >of your RAM memory. Hard disks have mechanical
> parts that allow to seek =3D
> >to a=3D20
> >particular position on the magnetic storage media
> and to read/write =3D
> >data.=3D20
> >This make them relative lazy. A RAMDisk can read
> and write the same data =3D
> >to=3D20
> >upon 30-60 times faster than a hard disk ! However,
> the data stored in =3D
> >your=3D20
> >RAM is "volatile" : it disappears when you cut off
> the power to the RAM=3D20
> >memory, with other words, if you turn off your
> system. This applies to =3D
> >the=3D20
> >content of the RAMDisk too !"
> >
> >ALEX
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
********************************************************
This weeks sponsor Vizioncore, Inc.=20
--> vc-iMonitor - Performance Monitoring, Control & Reporting=20
--> vc-iControl - Desktop & Start Menu Management & Reporting=20
--> vc-iMapper - Drive, Printer & COM Management & Reporting=20
http://vizioncore.com/products.html=20
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
********************************************************
This weeks sponsor Vizioncore, Inc.
--> vc-iMonitor - Performance Monitoring, Control & Reporting
--> vc-iControl - Desktop & Start Menu Management & Reporting
--> vc-iMapper - Drive, Printer & COM Management & Reporting
http://vizioncore.com/products.html
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
Other related posts:
