[Bug 1533639] Re: [ubuntu-cpc] please make /tmp a tmpfs in RAM

Dustin Kirkland  dustin.kirkland at gmail.com
Thu Jan 14 14:04:38 UTC 2016


** Description changed:

  In Ubuntu, we have always cleared /tmp on every boot.
  
  As such, on servers, by default /tmp should actually be a tmpfs entirely
  in RAM, when there is enough memory in the system.  This threshold
  should be configurable by the end user (in cloud-init?), and default
- threshold of ~2GB.
+ threshold of ~3GB.
  
  Read about tmpfs here:
  https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt
  
  This has several advantages, mainly:
   * Performance - much faster read/write access to data in /tmp
-    - especially if your disk is spinning media
-    - and if you're on SSD, this feature extends the life of your flash by reducing your NAND flash writes
+    - especially if your disk is spinning media
+    - and if you're on SSD, this feature extends the life of your flash by reducing your NAND flash writes
   * Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
   * Power consumption - storing information in memory is more energy efficient than reading and writing to disk
  
  In scenarios where more space in /tmp is needed than available, one can
  compliment that tmpfs with 'sudo apt-get install swapspace' which will
  dynamically create/delete swapfile as necessary.  See:
  http://manpg.es/swapspace

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1533639

Title:
  [ubuntu-cpc] please make /tmp a tmpfs in RAM

Status in livecd-rootfs package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu, we have always cleared /tmp on every boot.

  As such, on servers, by default /tmp should actually be a tmpfs
  entirely in RAM, when there is enough memory in the system.  This
  threshold should be configurable by the end user (in cloud-init?), and
  default threshold of ~3GB.

  Read about tmpfs here:
  https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt

  This has several advantages, mainly:
   * Performance - much faster read/write access to data in /tmp
     - especially if your disk is spinning media
     - and if you're on SSD, this feature extends the life of your flash by reducing your NAND flash writes
   * Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios
   * Power consumption - storing information in memory is more energy efficient than reading and writing to disk

  In scenarios where more space in /tmp is needed than available, one
  can compliment that tmpfs with 'sudo apt-get install swapspace' which
  will dynamically create/delete swapfile as necessary.  See:
  http://manpg.es/swapspace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1533639/+subscriptions



More information about the foundations-bugs mailing list