On Tue, 2010-03-16 at 11:05 +0200, Avi Kivity wrote:
quoted text
> > Not really.  In many cloud environments, there's a set of common 
> > images that are instantiated on each node.  Usually this is because 
> > you're running a horizontally scalable application or because you're 
> > supporting an ephemeral storage model.
> 
> But will these servers actually benefit from shared cache?  So the 
> images are shared, they boot up, what then?
> 
> - apache really won't like serving static files from the host pagecache
> - dynamic content (java, cgi) will be mostly in anonymous memory, not 
> pagecache
> - ditto for application servers
> - what else are people doing?

Think of an OpenVZ-style model where you're renting out a bunch of
relatively tiny VMs and they're getting used pretty sporadically.  They
either have relatively little memory, or they've been ballooned down to
a pretty small footprint.

The more you shrink them down, the more similar they become.  You'll end
up having things like init, cron, apache, bash and libc start to
dominate the memory footprint in the VM.

That's *certainly* a case where this makes a lot of sense.

-- Dave

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/