Re: Updated bootchart (rev1543)

Since the nbd image is read-only, can't we tell the kernel to cache
every block that it reads from it, so that it only needs to read each
block once, if the RAM suffices?

If the kernel already does that automatically, maybe *somehow* enabling
readahead would help? Or maybe a bigger block size?


Btw, I'd be interested to see how nbd-proxy affects low-end client
performance, e.g. PIII / 64 RAM. Stéphane, when the optimizations are
done, could you please notify me to do some testing?

-Alkis

Στις 20-01-2010, ημέρα Τετ, και ώρα 09:52 -0500, ο/η Gideon Romm έγραψε:
> Well, evidently it was nbd-proxy's fault. stgraber's nbd-client
> bootchart has it at only a couple of seconds, which just goes to show
> you how important it is to have the fastest reads possible from the
> network image.
> 
> Perhaps we should create an option on the server to copy the chroot
> image to RAM for export? Something like /var/cache/ltsp/images ?
> 
> The server would need a script to copy it on boot and to make sure that
> inetd is configured with the right path. Hmm... maybe something for the
> "extras" category.  :)
> 
> -Gadi



------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net