/tmp on tmpfs

[Mark Shuttleworth]

I know this is a discussion for Hoary, but nonetheless I'm curious, how 
can this be a good thing when RAM is your best ticket to performance?

What happens when you fire up a RAM-intensive app, like a database?

Fabio Massimo Di Nitto wrote:

>On Wed, 25 Aug 2004, Thom May wrote:
>
>  
>
>>It seems like current best practise is to run /tmp on a tmpfs - it's clean,
>>it's fast and it's nicely limited to half your available ram, ensuring that
>>you can't fill a disk by dumping crud in /tmp.
>>Does anyone know any reasons why we shouldn't do this by default?
>>    
>>
>
>The only reason i can see for not doing it is when there is not too much
>ram available. What about implementing it as an option?
>
>Fabio
>
>  
>

-- 
Try Debian GNU/Linux. Software freedom for the bold, at www.debian.org
http://www.markshuttleworth.com/