Wednesday, December 17, 2008

[ Cloud Computing ] Re: why virtualization?

Dan,
It is an interesting observation. Let me try to reconcile the two tenets.
If we look at this problem from 'bin packing' point of view, both tenets seem to complement each other.
Bin packing problem is an old operations research problem about packing several bins of known volumes with multiple smaller (by Volume) objects. To apply this model to the grid world: let us think of grid nodes as bins above, let us interpret bin volume as computational capacity of a node, let us think that computational tasks/applications are the objects with which we pack the bins(nodes).
Then this 'bin packing view' of grid computing becomes: how to allocate multiple computational tasks to several nodes in a near-optimal way (given certain constraints). This problem is NP complete, so we can strive only for near optimal allocation. The closeness to optimum is dependent on the size of the tasks: the smaller they are the better (more densely) we can pack the cluster.
So, having smaller virtualized tasks (tenet 1) allows us to get better overall optimization (aggregation is your terms) (tenet 2).
Boris


--- On Wed, 12/17/08, Dan Kearns <dan.kearns@gmail.com> wrote:

> From: Dan Kearns <dan.kearns@gmail.com>
> Subject: [ Cloud Computing ] why virtualization?
> To: cloud-computing@googlegroups.com
> Date: Wednesday, December 17, 2008, 9:05 AM
> Out of curiosity.... it seems to me that two pretty
> fundamental tenets of
> cloud computing are contradictory:
>
> Virtualization: a mechanism to get better utilization of
> existing hardware
> when loads are generally smaller than node capacity, or
> spiky in the time
> domain
>
> Griddiness: (for lack of a better word) the idea that
> appropriate cloud
> designs support massive scale, and do it by aggregating
> many small+cheap
> failure-prone compute units with smarter software
>
> If the goals are to have smarter software and maximize
> utilization (or
> minimize power consumption for equivalent compute
> capacity), then why
> introduce the constant runtime overhead of virtualization
> instead of, eg
> using smaller more power-efficient compute-unit designs and
> making the
> hardware controllable by software?
>
> Am I missing something, or is virtualization a tactical
> answer and therefore
> a short-term solution, and not a great place to start
> building management
> frameworks (for example) on top of?
>
> -d
>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Cloud Computing" group.
To post to this group, send email to cloud-computing@googlegroups.com
To unsubscribe from this group, send email to
cloud-computing-unsubscribe@googlegroups.com
To post job listing, send email to jobs@cloudjobs.net (position title, employer and location in subject, description in message body) or visit http://www.cloudjobs.net
To submit your resume for cloud computing job bank, send it to resume@cloudjobs.net.
For more options, visit this group at
http://groups.google.ca/group/cloud-computing?hl=en?hl=en
Posting guidelines:
http://groups.google.ca/group/cloud-computing/web/frequently-asked-questions
This group posts are licensed under a Creative Commons Attribution-Share Alike 3.0 United States License http://creativecommons.org/licenses/by-sa/3.0/us/
Group Members Meet up Calendar - http://groups.google.ca/group/cloud-computing/web/meet-up-calendar
-~----------~----~----~----~------~----~------~--~---

No comments: