· Naughties
· · 2004
· · · October
· · · · 19 (1 entry)

Per-CPU Pricing is B.A.D. · To­day in the news, re­ports that Mi­crosoft per-CPU pric­ing will treat multi-cored CPUs as one. The fact that in­tel­li­gent peo­ple should even have to think about this is fur­ther ev­i­dence, if any were need­ed, that per-CPU soft­ware pric­ing is Bro­ken As De­signed. To start with, it’s un­sta­ble in the face of Moore’s law and things like multi-coring. Se­cond, and this ar­gu­ment is re­al­ly unan­swer­able, it’s rad­i­cal­ly de­cou­pled from both the cost to the ven­dor and the val­ue to the user. For in­fras­truc­ture, the per-employee pric­ing that we’re try­ing here at Sun out seems to be the best bet for cap­tur­ing the buy­er val­ue. There are some oth­er class­es of ap­pli­ca­tions that de­liv­er a lot of val­ue but are used by small group­s; CRM, tra­di­tion­al BI (but my last com­pa­ny Antarc­ti­ca is try­ing to break that mold), trader’s-desk sys­tem­s. For small-group soft­ware per-identified-user or per-parallel-user can each some­times make sense. But I am com­plete­ly at a loss to think of a sin­gle soft­ware sce­nario where per-CPU pric­ing is ra­tio­nal or de­fen­si­ble.
author · Dad · software · colophon · rights
Random image, linked to its containing fragment

By .

I am an employee
of Amazon.com, but
the opinions expressed here
are my own, and no other party
necessarily agrees with them.

A full disclosure of my
professional interests is
on the author page.