Killing the Business Desktop PC Softly
by Johan De Gelas on July 19, 2007 3:00 AM EST- Posted in
- IT Computing
Blade PCs
Next up is the blade PC. The challenge is to make sure that the blade PC and the thin client consume less energy together than a typical business desktop. The big advantage of a blade PC is that all PCs draw from the same the power supply, which allows for the use of a more efficient power supply. HP has designed an enclosure that can house up to twenty blade PCs in a single 3U rack mount chassis, all of which are powered by the same redundant 600W power supply. That means that each blade PC consumes less than 30W.
The HP BladeSystem bc2000 and bc2500 consist of:
If you only need a 1.2 GHz Athlon 64, it becomes less clear why you would allocate a blade PC for each user. You might be better off with VDI for example (see below). It might seem like nitpicking, but if you want to add a full rack of relatively modern PCs with dual core CPUs, the system administrator of the data center has to cope with another 12-14 KW (bc2500). If you chose the bc2000 blade, you are looking at only 7.6KW per rack. Clearly there is nothing magical about blade PCs: a 50W blade PC and 15W-30W thin client are not going to save much power compared to a desktop with the same (low voltage) dual core CPU.
Let's take a closer look at the blade PC.
The HP blade PC bc2000
It is a pretty elegant and slim design with a small heatsink on top of the CPU, and two SO-DIMMs for memory expansion. If you don't like your blade PC to be headless, you can add an old Lynx EM4+ video chip which supports an 800x600 resolution when you access the blade PC directly.
Adding a video chip to the blade PC
The video chip plugs into the black "IDE-like" connectors. The second generation of blade PCs still has room for improvement: why use a hard disk if your data is going to be saved on centralized network storage? Solid state drives were probably too expensive at the time of the new blade PC design, but basically the design right now has room for improvement.
Next up is the blade PC. The challenge is to make sure that the blade PC and the thin client consume less energy together than a typical business desktop. The big advantage of a blade PC is that all PCs draw from the same the power supply, which allows for the use of a more efficient power supply. HP has designed an enclosure that can house up to twenty blade PCs in a single 3U rack mount chassis, all of which are powered by the same redundant 600W power supply. That means that each blade PC consumes less than 30W.
The HP BladeSystem bc2000 and bc2500 consist of:
- Low voltage AMD Athlon 64 X2 Dual-Core 3000+ processor (1.60 GHz 2x512K L2) (bc2500) or AMD Athlon 64 2100+ (1.2 GHz 512K L2) (bc2000)
- ATI RS690T/SB600 w/integrated DirectX 9 compliant graphics
- Up to 2x2GB 667 MHz DDR2 SDRAM
- 2.5" 80GB 5400 rpm SATA 1.5 Gb/s
- 100 Mbit Ethernet (Broadcom 5906M)
If you only need a 1.2 GHz Athlon 64, it becomes less clear why you would allocate a blade PC for each user. You might be better off with VDI for example (see below). It might seem like nitpicking, but if you want to add a full rack of relatively modern PCs with dual core CPUs, the system administrator of the data center has to cope with another 12-14 KW (bc2500). If you chose the bc2000 blade, you are looking at only 7.6KW per rack. Clearly there is nothing magical about blade PCs: a 50W blade PC and 15W-30W thin client are not going to save much power compared to a desktop with the same (low voltage) dual core CPU.
Let's take a closer look at the blade PC.
The HP blade PC bc2000
It is a pretty elegant and slim design with a small heatsink on top of the CPU, and two SO-DIMMs for memory expansion. If you don't like your blade PC to be headless, you can add an old Lynx EM4+ video chip which supports an 800x600 resolution when you access the blade PC directly.
Adding a video chip to the blade PC
The video chip plugs into the black "IDE-like" connectors. The second generation of blade PCs still has room for improvement: why use a hard disk if your data is going to be saved on centralized network storage? Solid state drives were probably too expensive at the time of the new blade PC design, but basically the design right now has room for improvement.
Facebook
Twitter
RSS
39 Comments
View All Comments
smokenjoe - Wednesday, July 25, 2007 - link
I just thought I would post some end user experience as these are not all that common. We had an intel based thin client. When they were fist implemented last year they were OK slower than the dated computers they replaced but usable. Unfortunatly as time went oth they started having more and more issues to the point that it was common to have only one working thin client out of 6. We had to boot the clerks off their old PIII computers from the dark ages because they were the only ones that worked. People literally jumped for joy when we got the PC's back.Without being part of the IT department it is hard to say where the fault was but at the bare minimum make sure you have people that have the training and security privileges to fix problems any time they are needed. I had multiple reports of "I cant fix that I dont have the security privileges we will have someone fix it on Monday."
Thank god they did not think the clerks important enough to upgrade or we would have been lost.
yanman - Monday, July 23, 2007 - link
Another alternative which is available through a mix of technologies is removing only the local storage of your corporate desktop fleet and replacing this with a PXE-boot solution. There are vendors that can allow iSCSI boot of XP installs via a proprietary solution using PXE.i.e. Dell Optiplex with onboard GbE, boots from PXE, loads iSCSI stack, mounts guest LUN on the SAN for it's XP image, boots. Possibly you could leave the local hard disk in and use it only for swap space.
Advantages
- Less forced change on the users
- Better workstation performance
- Retains the thin-client advantages of ensuring all data is on the SAN
Disadvantages
- Can significantly increase SAN and network utilisation
- Slightly exotic setup that may not be fully supported by the hardware vendor.
Ajax9000 - Thursday, July 19, 2007 - link
Could you please spell out VDI on page 9. I knew pretty much what was being talked about, but I still had to Google to be sure.The workstation blades are an interesting development. Would it be possible to do VDI over workstation blades?
I ask because where I work (a government department) went Citrix in about 2001. At that time performance was reasonable in Head Office, but flaky in the handful of regional offices. We had thin clients, skinny clients (PCs stripped down to act as thin clients -- to save on TCA of course), and fat clients for specialised uses. It worked quite well -- I'd run 20MB+ spreadsheets under Citrix and use a fat client for publishing & graphics apps that wouldn't run under Citrix.
The only problem was making sure IT didn't downgrade you from fat client. :-)
But the government then amalgamated us with some other agencies (with standard PC setups) and we went from ~800 staff to over 2500 staff with many regional offices with poor network connections. And there was much more specialised uses such as greatly expanded GIS/mapping, web mapping, publishing, etc. Trying to get a sensible IT setup took three years ... and then there was another round of amalgamations with another round of IT integration issues that still haven't been resolved (and again involving lots more GIS/mapping, web mapping, etc).
So, would it be possible to do VDI over workstation blades as a way of distributing ARCinfo "floating" licences, Adobe apps, etc, across multiple sites rather than having dedicated workstations in "fixed" sites?
RandyDGroves - Thursday, July 19, 2007 - link
This was a nice detailed review of CCI, but completely missed the fact that IBM is using PC-over-IP technology from Teradici (www.teradici.com) instead of a Thin Client. Unlike software solutions such as ICA, RDP, and RGS; Teradici's PC-over-IP processors use hardware to bridge the video, audio, and USB traffic between the desktop device (called a Portal) and the blade workstation. This enables a perception-free experience in which the end user cannot detect that their PC has been remoted. Furthermore, since the Portal only has a hardware decoder chip, it is lower power than a Thin Client.For full disclosure, I am the CTO for Teradici and obviously biased. But, here are some links to recent articles in other publications that may be of interest:
Wall Street Journal - http://webreprints.djreprints.com/1722520524296.ht...">http://webreprints.djreprints.com/1722520524296.ht...
EETimes - http://www.eetimes.com/news/latest/showArticle.jht...">http://www.eetimes.com/news/latest/showArticle.jht...
The Register - http://www.theregister.co.uk/2007/06/06/teradici_b...">http://www.theregister.co.uk/2007/06/06/teradici_b...
JohanAnandtech - Thursday, July 19, 2007 - link
The briefing we got in IBM's blade HQ in Raleigh about the IBM HC10 was a lot more about the concept. The actual hardware and software was not discussed in detail. That is why I focused mostly on CCI, as I had been shown the exact specifications.florrv - Thursday, July 19, 2007 - link
As a network security manager for an F100, we've found a very useful niche for VDI technology: 3rd party developers.Rather than have a 3rd party connect directly into your dev environment, you set up a VDI environment and give them a controlled sandbox. This way, you can lock down what data goes back and forth to the 3rd party.
senseamp - Thursday, July 19, 2007 - link
As mentioned, this has been out for 8 years as SunRays.http://en.wikipedia.org/wiki/Sun_Ray">http://en.wikipedia.org/wiki/Sun_Ray
You can take your badge out, go to any place in the company with a Sunray (like drop in office), put your badge in, and it will pop up the desktop where you left off. Unix (such as Solaris) is designed from ground up for this kind of work (multiple users running on same OS with remote display), so it works very well, if the network is behaving well. With star/open office and firefox/thunderbird, that's good enough for most office work, and if you need a lot of performance, you can dispatch jobs to bigger machines or compute farms in the company.
szaijan - Thursday, July 19, 2007 - link
Sun has been pushing the thin client architecture for years, yet there's no mention in the article. Having worked on multiple Sunray clusters, and many PC netwroks, I have the say the thin client setup is much better for day-to-day office and e-mail work, simply based on the lack of overhead in installation, bug resolution, boot times, et. al. Cost is much lower overall. The downside is that network problems make work impossible, while you can still utilize a PC when the network is down or overloaded. A decent netwrok infrastructure makes this a minor issue.All that said, CAD, Photoshop, 3D Modeling, et. al., while not impossible, are badly hampered by the mouse latency, and the precision needed for such endeavors just isn't there. Of course you can just add a work station to the network for employees who require that level of client power.
Adul - Thursday, July 19, 2007 - link
We've been on a mission to getting rid of our thin clients as they been a source of pain since they keep getting infected with viruses, we can't patch them with normal updates, etc.JohanAnandtech - Thursday, July 19, 2007 - link
Very interesting. As you might have noticed, there are a lot "should" and "might" in the article :-). Could you tell me what kind of thin clients you are using? Running XP Embbedded? Why can't you patch them?