AMD's 12-Core Chip Cuts Software Licensing Costs
CWmike writes "AMD released on Monday its 12-core chip code-named Magny-Cours, doubling the number of cores over the previous-generation Opteron chip. While a doubling of performance is nice, another key benefit delivered by a chip with a dozen cores may be in reducing software costs. For Matt Lavallee, director of technology at MLS Property Information Network, a company that supplies real estate data, upgrading to the 12-core Opteron chip from his current quad-core chips will allow him to cut the number of servers — and his software licensing fees. While the 12-core chip costs a little more than an eight-core chip, it's 'nowhere near as much as a SQL server costs,' said Lavallee, who has been beta-testing the new chips. MLS operates 60 servers, and Lavallee said he could theoretically cut the number of servers by half but will likely reduce his server count by a third with the chip upgrade."
Reader adeelershad82 adds that AMD is hoping the new Opterons will compete with Intel in the high-volume server market.
Has MS updated their licensing to be "per-core" instead of "per-CPU"?
http://www.bynarystudio.com
Fair enough, but my Linux licensing costs won't change!
From hell's heart I fstab at /dev/hdc
Almost all of the enterprise software we buy charges by the CPU and by the seat. For this purpose a CPU core is the same thing as seperately socketed CPU. Whatever about OS savings I think you'd save more in hardware and running costs than you would on software.
I never get used to these constant resurrections
Oracle, MS and others change the licensing to require a charge per core.
No sig for you!!
Is that software licensing is a rip off to begin with.
They license per-core, so more cores per CPU can be more costly.
Why the heck is he paying anything? Just use MySql and be done with it. It is certainly easier to use/setup/maintain than that crappy SQL Server stuff. And it is free to boot! sheesh.
In my experience, it's rare for SQL Servers to be CPU bound, they're almost invariably IO bound, and having more cores won't help you when your disks are the bottleneck. I could see excitement over lowering per-machine costs for something like a renderfarm, but it doesn't seem likely to materialize for Databases.
I read the internet for the articles.
Very clever, AMD. Naming your chip after a location in Europe as usual, but this time making it able to be read as "Many-Cores" (or possibly more accurately "Many-Core", I don't really know how to pronounce French words). Very clever indeed...
Will I need to buy more SCO licenses for this one chip? This could get expensive.
Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
What are these? Is this something that afflicts Windows people still?
Stick Men
Virtualization is a huge market for these cpus as well.
Anandtech has an excellent review of the new chip. The AMD chip is compared against the latest Xeon. In some situations such as OLTP and ERP, the AMD offering lives down to it's name Mangy Cores. In HTP and data-mining, Anandtech gives the nod to AMD.
So choose depending on your needs.
Think VM (VmWare/Xen/Solaris Zones) instead of parallel applications...Multi-core CPUs are great for server consolidation. We went from a row of 10 full racks of Sun gear down to 10 T2+ blades + a SAN over the last 18 months. Database / webserver / Java app server, you name it, the T2+ handles it all!
If only "common" sense was actually that common...
Really? You mean, as computers get faster you *might* need fewer of them?
No really. Please provide evidence for the thesis that as computers get faster, people need fewer of them.
Second point. It's usually the I/O performance anyway. A 12 core server is unlikely to be able to push as much throughput as 3 quad cores, given the same I/O technology.
Deleted
As computers get faster, software becomes more bloated and runs slower.
Not a Twitter sockpuppet... but I wish I was.
One of the coolest things about this stuff is that inside of one dual-processor workstation you can set up a whole datacenter worth of VMs, and model how the pieces interact without fiddling with racks and cables. You can build up a redundant database, fileserver or iSCSI server solution (or all three!) and see how it handles failover and failback. The simulated clients that apply stress can be VMs in the same box. You can even float a cloud of routers and see how they handle various BGP commands. Pretty neat stuff.
Help stamp out iliturcy.
Since multi-threading is so hard to do right, most of what you are going to do is consolidation.
So instead of having 6 separate servers, you just shove buttloads of RAM in a single server and set up a SAN for your data storage, and move all 6 servers to one box. You can even split it up further than that - if you have a couple servers that need to be separate from each other, but don't really need a lot of processing power, you can put those on a single core apiece. So you could potentially consolidate up to 12 servers into one box with virtual servers. More than likely you'll only get 6 or 8 out of it, because dual cores do help a lot, but still there's the potential to turn two racks of servers into one server and a SAN.
You save on space, you save on energy, and you ultimately save on hardware (though SANs are expensive, so if you don't need the speed you could go to a standard NAS setup). To expand your data storage you just need to expand your SAN, so you can add servers and storage independently of each other. All of these are major up sides to going this route.
Going from a 60 server setup to a 10 server setup has a massive potential for savings.
Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
Someone needs to put "Advertisement" at the top and bottom of these posts of PR copy.
Time to render 30 minute Video CD image (at VHS resolution) on 1999 mid-high level PC (cost £1200): 10 hours approx, PC effectively unusable for other purposes.
Time to render 2hr DVD image (at std DVD resolution) on 2008 low end PC (cost £350): 30 mins approx, PC also playing music/video, web browsing, ripping CDs etc. at the same time.
The effect of 'bloat' is often overstated.
And if 100% of what was done with computers scaled like that, you'd have made a great point.
Well, I think you've missed an important part of my point.
What I described is a good illustration of a fairly common scenario - one fairly heavy task going on in the background and a variety of less demanding tasks in the foreground. Although other demanding background tasks would not have increased in speed as much as video rendering, the general principle holds good that with a cheap modern PC you can run something really demanding at the same time as using the PC for several other foreground purposes; going back a ten years this was largely impossible even with higher end machines. So bloat is not cancelling out hardware advances.