<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Robert McNamara wrote:
<blockquote
cite="mid:1aaba6e90911051016s42d47f9di95dd16179e28240f@mail.gmail.com"
type="cite">
<pre wrap="">On Thu, Nov 5, 2009 at 10:13 AM, Tony Lill <a class="moz-txt-link-rfc2396E" href="mailto:ajlill@ajlc.waterloo.on.ca"><ajlill@ajlc.waterloo.on.ca></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Do you mean that myth is storing cover art and other stuff in the
theme cache, besides just the theme graphics?
</pre>
</blockquote>
<pre wrap=""><!---->
Yes, it does. (.22) The scaled and transformed (effects applied)
cached images are saved in the themecache.</pre>
</blockquote>
What kind of performance hit does this put on a front end machine that
is net booted, if multiple gigs of data are needed for the theming? I
was planning on upgrading to a Zotac Ion Atom 230 based system net
booting over a 100Mb network, but if themes are going to start loading
multi-gigabytes of data across the network, that may work as well. Or
will it? I guess since it is only a few images per screen, no one
screen load would need a whole lot of data.<br>
<br>
Likewise, my other thought was to use a small SSD drive or SDHC card to
boot the FE (the idea is to have no moving parts, thus no noise), but
there I'd thought I'd only need maybe 2 to 4 Gb total space to install
the OS on, so would this mean I had to have a bigger (read more
expensive) drive just to hold the theme cache? Like I said, this is a
FE only, all my media would be on the MBE. Could not the theme cache
be there as well (without having to muck about with trying to figure
out how to auto mount samba or NFS shares which I've never managed to
get to work properly). After all, the MBE is serving up all sorts of
other media, why not the imagery for the UI? Provided the network hit
isn't too bad (see first question), it would seem to make sense to
leave such heavy storage for the backend.<br>
<br>
Jeff.<br>
</body>
</html>