Move to a Mainframe, Earn Carbon Credits
BBCWatcher writes "As Slashdot reported previously, Congress is pushing the U.S. Environmental Protection Agency to develop energy efficiency measures for data centers, especially servers. But IBM is impatient: Computerworld notes IBM has signed up Neuwing Energy Ventures, a company trading in energy efficiency certificates, in a first for "green" computing. Now if your company consolidates, say, X86 servers onto an IBM mainframe on top of slashing about 85% off your electric bill each megawatt-hour saved earns one certificate. Then you can sell the certificates in emerging carbon trading markets. IBM's own consolidation project (collapsing 3,900 distributed servers onto 30 mainframes) will net certificates worth between $300K and $1M, depending on carbon's market price. Will ubiquitous carbon trading discourage energy-inefficient, distributed-style infrastructure in favor of highly virtualized and I/O-savvy environments, particularly mainframes?"
I do find it ironic that computing started out with large mainframes, and now it seems more and more likely that the majority of computing needs in the future will be met by terminals connected to mainframes via virtualization.
The whole concept of "carbon neutral" and off-setting your carbon emissions for whatever reason seams kind of lame to me. Instead of continuing to do things that cause global warming while doing other things to supposedly reduce your "carbon footprint", why not just try to eliminate or reduce the problems in the first place? It's not just individuals, it's the whole mindset of society. Instead of going for carbon-neutral server farms, why not develop cleaner alternative electricity options to power those server farms? Solar power could do a lot, but we'd rather earn carbon certificates. It just doesn't make sense.
...and reducing the amount of pollution we spew into the atmosphere is beneficial to us and to the environment, global-warming boogeyman or not.
Peak oil is going to do the job instead.
Deleted
At the moment there is no permission required to pollute, you could pump as much CO2 into the air as you like. Well, instead of that the government says:
1: You need permission to pollute.
2: You get those permissions from the carbon credit markets.
3: You have to buy them at whatever they cost in that market every year.
4: You can sell permissions if you have more than you need.
Then the government auctions enough credits to represent a slight reduction in the overall production in CO2. Each credit might represent one tonne of CO2. Then each year the government reduces the numbers of credits available in the market. The cost of a credit then increases simply due to the reduction in supply or the increase in demand.
As the cost of emitting the CO2 increases, companies will switch to alternative solutions, choosing whichever they like best.
Of course, this only works if politicians aren't completely corrupt or utter morons, as seems largely to be the case. In that case they might give companies credits and allow them to sell them on the markets, it's basically free money to those companies which receive the credits.
Deleted
http://www.howstuffworks.com/question192.htm This sounds like a tremendously poor miles-per-gallon rating! But consider that a 747 can carry as many as 568 people. Let's call it 500 people to take into account the fact that not all seats on most flights are occupied. A 747 is transporting 500 people 1 mile using 5 gallons of fuel. That means the plane is burning 0.01 gallons per person per mile. In other words, the plane is getting 100 miles per gallon per person! The typical car gets about 25 miles per gallon, so the 747 is much better than a car carrying one person, and compares favorably even if there are four people in the car. Not bad when you consider that the 747 is flying at 550 miles per hour (900 km/h)! Better than one person in Prius.
http://www.toyota.com/prius/ The Prius boasts an EPA-estimated combined city/highway rating of 46 miles per gallon Two or more in people in Prius will beat a 747. Or maybe not, loading up a car will cause the total miles per gallon to drop as the weight increases. Maybe you need three people in a Prius to be safe. But most cars have one person and lower mpg, so it's not like 747s are worse on average than cars.
You don't need to Google all this stuff yourself of course, you just pick the cheapest way to travel and rely on market forces to make the most energy efficient way the cheapest. Which should be true so long as oil is expensive enough to make it a non neglibable part of total costs.
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
In the end we'll end up with just 5 huge mainframes in the world as foretold by the IBM executive in the 50's? (can't remember where he was quoted).
As a general rule, if you're building a business computer and want to save as much as electricity as possible, the most highly virtualized (and virtualizable) platform wins. So attributes like massive caches and screaming I/O help enormously. (I think there was a Stanford study recently that figured this out.) Thus it's no surprise a modern mainframe is more energy efficient than anything else.
But in the Computerworld article referenced in the original story, IBM says the carbon program will also be available for its System p servers at some point in the future. My prediction is that you'll typically get fewer certificates if you move to System p versus System z, but it's likely businesses will do some of both depending on what sort of applications they're rehosting. There are some types of applications that will do better on System p, and there is some software that runs on AIX that doesn't run on z/OS or Linux.
Regarding SPARC it's impossible to say since Sun hasn't entered into any carbon credit auditing system yet. The IBM-Neuwing program is a first. However, my prediction is that you'll get even fewer certificates if you consolidate to SPARC. I say that simply because I assume IBM is acting in its own self-interest, and I'm sure they think the energy efficiency fight is one they can win against other vendors. In this case self-interest and environmentalism coincide. For any of these platforms, though, businesses will figure out whether the certificates favor certain platforms over others, and they'll do that application by application (or application function by application function). And many other factors will go into the decision as well, although most of those factors pull in the same direction as energy efficiency, such as software charges. One could even imagine that before long server vendors lagging in the energy efficiency department will start bundling carbon certificates with their servers in order to compete. Thus IBM adopting this program is a smart way to respond to an untapped market need and to raise the effective price of competing servers compared to IBM's. Very smart move.
By the way, the world has totally flipped on its head, and it would be extremely misleading to say an IBM mainframe is "proprietary" and X86 (for example) isn't. What does proprietary mean? You can run pure 100% GPL Linux on an IBM mainframe -- Debian, Slackware, CentOS, etc. -- and you don't even need a closed source driver as you usually need for X86 servers. IBM publishes extreme instruction-level detail in a free book called Principles of Operation, and it's so detailed and thorough that the open source community created an implementation of the instruction set called Hercules that actually works compared to still imperfect efforts like Bochs and QEMU. (Although IBM may assert patent claims on its processor architecture.) One company is porting OpenSolaris to System z, and they didn't even have to ring up IBM. In comparison, Intel and AMD also may assert patent claims, and AMD is suing Intel for alleged monopolistic behavior. Neither Intel nor AMD publish PoO-type documents (to that level of detail). Then there's Microsoft Windows, and it's hard to think of any more proprietary OS than that.
Also, IBM changed the way it charges for z/OS software about 7 years ago. Now almost everything is charged by the amount you actually use, something IBM calls Variable Workload License Charge (VWLC). If you run a little bit of DB2 in one LPAR (partition) but a lot of IMS in another, then you pay a little for DB2 and more for IMS. You also control exactly what you consume using something called softcaps, and you can set those either per-LPAR or for a group of LPARs. One interesting little twist to mainframe subcapacity licensing is that, if you need a little bit of WebSphere (and a lot of other IBM products), the lowest entry price (smallest license you can order) is for z/OS. You can order as little as 1 "Value Uni
Not sure what type of data center you are in, but we still need 3-phase power for some of our non-zSeries boxes. Most blade servers require it. Our non-zSeries boxes generate more heat and draw more power than our 2 zSeries servers combined and we only have about 70 small Intel/AMD based system. True you can't run x86 binaries on a zSeries, but you can't run zSeries binaries on a x86 and didn't seem to be a problem when everybody started to migrate away from the mainframe. Why should it be a problem to migrate back? You can run most Linux/POSIX based code by just re-compiling it under Linux on zSeries. Windows code will need to be changed, maybe. I am assuming that you could run WINE under Linux on zSeries and thus that would allow you to run anything that can run under WINE. But I would not want to see what the performance would look like. :)
Now, if you want to run your program under z/OS (one of the operating systems that you can run on zSeries) then you have some code re-writing to do, unless you are running Java code. Which should run with very little if any changes under z/OS.
Unless you are running Linux only, and only truly free Linux based code, and you are running with out support (which you can do on zSeries also) you still need to license software on x86. The licensing fees for z/OS include support also and in some cases upgrades. Whereas Windows based software (especially Windows itself) only includes the ability to run the software and sometimes software upgrades. If you want support you must pay extra and for most Windows based software you have to pay to upgrade.
As for DASD, if you are running Linux only you can connect any SAN that support fiber channel to the mainframe. You only need "special" DASD if you plan to run z/OS.
The System Programming books are for z/OS, not necessarily zSeries. You don't need a z/OS system programmer to run Linux on zSeries.
In some instances you seem to be getting hardware (zSeries) and software (z/OS) requirements mixed up.