[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Server Specs: Compaq Evo W4000



Richard Ingalls wrote:

I'm looking at using the Compaq Evo W4000 as a K12LTSP server for 9 clients.
This is for a "writing" lab for grades 6 - 8, so they'll mostly use
OpenOffice and Mozilla.  Not much else.


OpenOffice and Mozilla are possibly the two most resource-hungry apps you can run, even for just 9 clients.



Server: * Intel® Pentium® 4 2.4GHz Processor with 512 L2 cache


yummy.


* 512MB ECC DDR Memory (ECC DDR266/PC2100)


nope, poke it up to 1GB at least.


   * 18.2GB SCSI 10,000 RPM (Atlas 10K318wls Drive)
   * Adaptec 29160 SCSI Ultra160 Controller (68 pin)
   * 533MHz Front Side Bus


mmm, yummy, drool...



* 16x DVD Optical Drive + Software * AC 97 16-Bit Audio * Built-In Premium Speaker


not important, nice though.


* Intel's Legendary 845 ECC DDR Motherboard


yummy.


* Intel Pro/100 VM Network Connection


8-) pity it's not gigabit, but it will be fine. Make sure your switch is a goodun.


* Dual Case-Cooling System


important. yummy.



Clients (9): * Intel® Pentium® II 450MHz Processor * 64MB SDRAM Memory * 6.4GB Hard Drive * CD-ROM Drive * 3.5" 1.44MB Floppy Drive * Onboard ATI 3D Rage Pro Video * Onboard 3COM Fast EtherLink XL * Crystal AC'97 Sound


Thin clients ? You won't need the HDD. However, you might want to do Local Apps, local Swap, and so on.. then the whole network will really honk along. This will make a very big difference to your overall performance, and to the future expandability of your network. You should easily be able to boot thin-clients with etherboot, and then migrate to local Apps when necessary/desired.



Again, I checked the on RedHat's compatibility list and all should be OK.


Any suggestions, comments?


It should all work out-of-the-box. The RAM will be an issue, particularly for 9 sessions of OpenOffice + Mozilla, and you will discover the system will load very quickly, but it will function. <wince>


I suggest you plug it all in, and place it in service, and then add an extra client in your office and work on having it do local apps, since you have plenty of CPU/RAM/HDD on the clients. If it all works, and the performance payoff is significant, you will be able to migrate the rest of your terminals to local apps easily and quickly once you have a working example.



All the best,
Steve






[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]