Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Spots who wrote (7271)	4/26/1999 9:12:00 PM
From: Clarence Dodge	Read Replies (1) \| Respond to of 14778

Spots Thanks for sharing your views on paging file memory allocation. (again) I have not understood your notion of isolated drive I just mean drives that have there own OS and require a restart to switch to. I agree that 'isolated ' is not an appropriate term. The more I work with my system the more I understand what you mean by Windows smearing everything everywhere. I've done a good bit of smearing myself as well by trying to have access to apps like Diskeeper, Backup Exec, Outlook Express in a centralized manner across two drives. I promise to never describe my disks as isolated any more.<g> I continue to recommend a paging file or files which aggregate at least twice the size of real physical memory. You used the word aggregate. In my case, with the two drives each with their own NT and 128 mb ram, are you saying 2 X 128 total across the two drives or 2 X 128 on each drive for a system total of 512 mb? Also should the initial size and maximum size be the same or handled in some other manner? There is absolutely nothing to be gained by allocating different page files to different instances of an OS. I would allocate them the same size on each drive in each instance Again, just to be clear, your saying, for me, 256 on NT drive A and another 256 on NT drive B? Also the 256 would be the maximum size then what would initial size be? Sorry to be dense here... Clarence

To: Spots who wrote (7271)	4/26/1999 10:08:00 PM
From: Zeuspaul	Read Replies (2) \| Respond to of 14778

Speaking of paging files..can we add RAID 0 to the mix? I am setting up a new NT work machine (with help) and want to try NT software RAID 0. The machine has three 10,000 RPM SCSI 9 gig drives. (and three 9 gig SCSI drives sharing a removable slot..two ROMOs and one Win95/KOT boot drive for specialized apps) NT 4.0 is installed in a 2 gig partition on the first hard drive. My question is should I stripe across two or three drives? My plan is to have NT and applications installed on the C drive. Then stripe the first gig on each of two additional drives. Can I get better performance if I add a one gig piece of the first drive to the stripe? Or is it better to leave the first drive to NT basics and the striped second two for file access? My thought is to configure the page file on the RAID 0 setup...also the work files for faster saves and callups and perhaps a couple of applications. The storage review article says to stay away from the boot drive with software RAID but limits? the comment to IDE drives? Would a second partition on the boot drive (to be used in the RAID 0 stripe) be considered the boot drive? The setup is supported with some significant processor power..dual XEON processors and a gig of RAM...SCSI III bus(LVD). Zeuspaul Some general NT RAID 0 info consensys.com A StripePartition is a RAID 0 partition that stripes data across two or more disk. This RAID scheme achieves the maximum in parallelism and the best performance, but provides no data redundancy. A StripePartition is typically used to hold data that must be accessed as quickly as possible, but does not require fault tolerance. Some examples include disk caches, video capture data, data warehouse applications, and temporary file storage. And from Storage Review's view of NT Software Striping storagereview.com 9 aug 98 review Windows NT Workstation 4.0 features a built-in function that allows spans of spaces on two different drives to be used in a striped configuration. Though NT's Disk Administrator is actually pretty flexible in allowing the user to create a striped pair in a variety of setups, the ideal configuration is the complete striping of all space between two identical drives..... When running a setup in real-word usage, however, the user should take care to minimize access of the boot drive- all applications should be installed to the striped pair as should NT's swapfile. Of course, all this headache could be avoided in several ways. An all SCSI setup (SCSI boot drive and two identical SCSI units in the striped pair) wouldn't be subject to the same limitation. You could add more ATA channels also, though if you're going to go out of your way to buy a controller and give up system resources for it, you may as well just use a FastTrak.