[vc_row][vc_column][vc_column_text]Lorem ipsum dolor sit amet, nec in adipiscing purus luctus, urna pellentesque fringilla vel, non sed arcu integer, mauris ullamcorper ante ut non torquent. Justo praesent, vivamus eleifend torquent, suspendisse etiam lorem vestibulum, vestibulum in lorem nec vel, sit curabitur dui ligula vehicula quam. Nec in neque mauris, enim hac risus in lorem. Mi risus, feugiat egestas nunc vehicula vehicula libero. Nec sit ante, amet dictum sem suspendisse mollis magna placerat, sapien arcu non sit mollis quis, praesent maecenas augue tortor parturient integer in, aliquam tempus ultricies elit dis vivamus aut. Ipsum non ut egestas in, suspendisse ut. Sodales sed cras. Et consequat viverra. Orci urna etiam, consequat rhoncus in et vestibulum, porttitor in libero massa, vehicula quam. Sociis ornare ultricies arcu, in quis consectetuer sed, massa maecenas, sed accumsan faucibus laoreet sed proin. Sit vivamus amet orci ornare sit metus.[/vc_column_text][vc_empty_space height=”40px”][mkdf_blockquote text=”Consectetuer in at varius fames posuere sagittis. Enim eget est augue aspernatur venenatis vitae, purus netus libero cras lorem, praesent.”][vc_empty_space height=”25px”][vc_column_text]Risus amet purus odio id, mattis diam vestibulum dolor orci, porttitor aenean cursus phasellus sit in eu, mollis vel, mattis hac libero vestibulum. Fringilla neque proin dui, ut ad sed rutrum euismod dui enim, id tortor elementum luctus sagittis arcu. Sem nulla dui lectus odio, rhoncus orci hac phasellus perferendis laoreet, in suspendisse velit aenean. Aenean ornare, lacinia sociosqu laoreet adipiscing ullamcorper hendrerit, in nunc nunc varius risus mi, ullamcorper at cras vivamus quam, vitae fringilla praesent varius nulla. Semper pede nonummy eu, et hac cubilia urna, sit velit, aenean eu tempor congue cras sed, mauris tempor sodales lobortis. Ipsum maecenas neque ligula mi purus iaculis, id turpis nisl duis. Gravida nunc nam dui.[/vc_column_text][/vc_column][/vc_row]
Tag Archives: analytics
Jevon’s Paradox
I’ve been finding it necessary to quote Jevon’s paradox several times lately and realized that I have NOT referenced it here. Quite simply, understanding Jevon’s paradox is essential to understanding cloud.
The concept of the paradox is that when we make something more efficient (for example gas in cars), the demand for that resource goes up (we move further into the exurbs because driving is cheaper). Notably, as Moore’s law drives computer efficiency up, we are using more and more computers. Specifically, I have more computers in my house every year even though the efficiency of just one smart phone far (far) exceeds power of my son’s Sinclair 1000.
In cloud computing, Jevon’s paradox points us to the expectation that the rush of applications and activity in the cloud will continue to accelerate. Since I expect competition and Moore’s law to drive increasing gains in cloud efficiency (and therefore customer advantageous price signals) the market will happily convert these utilization improvements into more and more interesting capabilities.
The cloud expansion means that we can sustain more providers entering the market. In fact, Jevon would tell us that more providers will likely INCREASE demand for cloud as competition and capacity put downward pressure on prices. [Q: where will they make up the margin? A: Adjacent Services]
The loser in cloud’s exploration of Jevon’s paradox are non-cloud deployments (Dell strategists are you listening?). These systems suffer because their ability to improve their efficiency is limited.
As I look down the road on cloud, I can see many opportunities for current applications to take advantage of cheaper cloud resources to provide even more value. For example, adding map-reduce analytics to scan a customer’s data can provide tremendous insights. Today, it’s a luxury like flying on the Concorde. Tomorrow, it will be part like hopping the Nerd Bird from San Jose to Austin – just a normal part of our daily lives.
Note: A shout out to Dave McCrory who introduced me to Jevon’s Paradox.
Are Clouds using Dark Cycles?
Or “Darth Vader vs Godzilla”
Way way back in January, I’d heard loud and clear that companies where not expecting to mix cloud computing loads. I was treated like a three-eyed Japanese tree slug for suggesting that we could mixing HPC and Analytics loads with business applications in the same clouds. The consensus was that companies would stand up independent clouds for each workload. The analysis work was too important to interrupt and the business applications too critical to risk.
It has always rankled me that all those unused compute cycles (“the dark cycles”) could be put to good use. It’s appeals to my eco-geek side to make best possible use of all those idle servers. Dave McCrory and I even wrote some cloud patents around this.
However, I succumbed to the scorn and accepted the separation.
Now all of a sudden, this idea seems to be playing Godzilla to a Tokyo shaped cloud data center. I see several forces merging together to resurrect mixing workloads.
- Hadoop (and other map-reduce Analytics) are becoming required business tools
- Public clouds are making it possible to quickly (if not cheaply) setup analytic clouds
- Governance of virtualization is getting better
- Companies want to save some $$$
This trend will only continue as Moore’s Law improves the compute density for hardware. Since our designs are leading towards scale out designs that distribute applications over multiple nodes; it is not practical to expect an application to consume all the power of a single computer.
That leaves a lot of lonely dark cycles looking for work.
Now all of a sudden, this idea seems to be playing Godzilla to a Tokyo shaped cloud data center. I see several forces merging together to resurrect mixing workloads.
- Hadoop (and other map-reduce Analytics) are becoming required business tools
- Public clouds are making it possible to quickly (if not cheaply) setup analytic clouds
- Governance of virtualization is getting better
- Companies want to save some $$$
This trend will only continue as Moore’s Law improves the compute density for hardware. Since our designs are leading towards scale out designs that distribute applications over multiple nodes; it is not practical to expect an application to consume all the power of a single computer.
That leaves a lot of lonely dark cycles looking for work.