On Wed, Jun 20, 2012 at 4:57 PM, Brian Wheeler <bdwheele(a)indiana.edu> wrote:
But in any case the I/O advantages have never been shown, despite
requests by myself and others.
I posted some example numbers earlier in this thread. e.g. make on an
already compiled firefox source was half the time on tmpfs compared to
ext4— even though the workload was all hot cache. Also its easy to
observe the write activity on tmp that happens even for short lived
files and reducing write load on SSDs was one of the main arguments
advanced for this change.
Well, yes and no. You also have to make sure you have enough backing
you're screwing yourself out of usable ram.
Yes, and the installer does this IIRC.
The problem here is that the
amount of /tmp by default is small by default so the tinkering with sizes is
actually more likely to be required that it was before.
Yes, this was why I said I didn't know if it was a good idea that
systemd leaves the default alone or not. I don't run any of my
systems that way.
If this change turns out to be problematic then I think this would be why.
Maybe for F19 I'll submit a feature that requires all X apps have to use
8-bit color (oooh, and private colormaps) since its will make network
rendering 3x faster and that what solaris used to do! Don't ask any
questions, though, because you can't possibly understand and I know it just
works for me.
You should just remove network transparency from the window system
entirely. No one needs that and besides VNC/Spice is good enough for