Bug#735927: general: X *always* crashes when ram is full
On Mon, Jan 20, 2014 at 12:29:28PM +0000, Kevin Chadwick wrote:
> previously on this list Roger Leigh contributed:
>
> > With an SSD, you really
> > don't want /tmp or swap on it;
>
> Why?, due to limited write cycles?
That's one reason, but the one I was thinking of was the shocking
performance. I accidentally disabled tmpfs on /tmp on my main
system with an SSD rootfs a few months back and was wondering
why I was experiencing such slow builds, desktop freezing for
seconds at a time, and other intermittent stalls. Turns out it
was thrashing the SSD since /tmp was on the rootfs. Enabling
tmpfs on /tmp resolved the problems, changing the performance
from dire to excellent. (I have the swap on a RAID1 LVM LV on
fast HDDs). This is a system with 8 cores @4GHz, 16GiB RAM,
over 16GiB swap, so should be pretty performant, yet /tmp on an
SSD made it crawl and freeze continually.
This is purely down to the slow write speed of the SSD I have
(Intel 320 128GB). If you have a faster SSD, maybe it won't be
an issue, but given the amount of junk being written to /tmp
when running a desktop environment and applications, from dozens
of tmp files and sockets to streaming video, it's likely it will
make a significant difference to make /tmp a tmpfs or HDD
filesystem.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
Reply to: