All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andres Lagar-Cavilla <andreslc@cs.toronto.edu>
To: snowflock_announce@cs.toronto.edu, xen-users@lists.xensource.com,
	xen-devel@lists.xensource.com
Subject: Announcing the first release of SnowFlock
Date: Fri, 12 Sep 2008 16:09:13 -0400	[thread overview]
Message-ID: <48CACC69.4070900@cs.toronto.edu> (raw)

Hi everyone,
we're releasing Snowflock to the general public. We're making a binary 
and source relase, under the GNU General Public License (GPL). The 
release is available at http://compbio.cs.toronto.edu/snowflock.

Briefly, Snowflock lets you clone Xen VMs into dozens of identical 
replicas running in different hosts. Snowflock can do this in less than 
a second and with very low runtime overhead. With Snowflock you can, for 
example, perform parallel computations on the fly by scaling 
"instantaneously" your computing footprint in a shared cluster. 
Snowflock is a research prototype, hence the 0.1 major-minor. A minimum 
degree of experience with Xen and Linux is necessary to use the system. 
The contact address for snowflock is snowflock-users@cs.toronto.edu

More technically:
Snowflock is our prototype implementation of the / Impromptu Cluster 
(IC)/ abstraction. In an IC, an application encapsulated inside a 
virtual machine (VM) is swiftly forked into multiple copies that execute 
on different physical hosts, and then disappear when the computation 
ends. ICs simplify the development of parallel applications and reduces 
management burden by enabling the instantiation of new stateful 
computing elements: workers that need no setup time because they have a 
memory of the application state achieved up to the point of forking. 
This approach combines the benefits of cluster-based parallelism with 
those of running inside a VM.

Snowflock provides swift parallel VM cloning that makes it possible for 
Internet applications to deliver near-interactive performance for 
resource-intensive highly-parallelizable tasks. Snowflock makes use of 
four key techniques: /VM descriptors/ (condensed VM images that allow 
for sub-second suspension of a running VM and resumption of a of 
replicas); a /memory-on-demand/ subsystem that lazily populates the VM's 
memory image during runtime; a set of / avoidance heuristics/ that 
minimize the amount of VM memory state to be fetched on demand; and a 
/multicast distribution/ system for commodity Ethernet networking 
hardware that makes the overhead of instantiating multiple VMs similar 
to that of instantiating a single one.

Use, enjoy, give us some feedback, and contribute to mankind :)
The Snowflock team

             reply	other threads:[~2008-09-12 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 20:09 Andres Lagar-Cavilla [this message]
2008-09-12 20:42 ` Announcing the first release of SnowFlock Javier Guerra
2008-09-13 23:37   ` [Xen-users] " Andrés Lagar Cavilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48CACC69.4070900@cs.toronto.edu \
    --to=andreslc@cs.toronto.edu \
    --cc=snowflock_announce@cs.toronto.edu \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.