On Wed, Jan 27, 2016 at 08:16:17AM +0100, Martin Pitt wrote:
> Robie Basak [2016-01-25 19:25 +]:
> > 1) Make the option available but non-default on cloud images.
> > 2) Make the option available and default on cloud images (so opt-out).
>
> As for "making available": you can append "none /tmp
Robie Basak [2016-01-25 19:25 +]:
> 1) Make the option available but non-default on cloud images.
> 2) Make the option available and default on cloud images (so opt-out).
As for "making available": you can append "none /tmp tmpfs defaults 0 0"
to /etc/fstab, as already mentioned. But if modify
Hi Ben,
On Mon, Jan 25, 2016 at 06:56:38PM -, Ben Howard wrote:
> After considering the robust discussion, I would like to propose that
> we move forward with this change via Cloud-init with some sane
> defaults (i.e. it is _NOT_ running in a container and memory is
> greater than 2GB of RAM).
On Jan 22, 2016 11:52 AM, "Colin Watson" wrote:
>
> On Fri, Jan 22, 2016 at 09:09:10AM -0600, Dustin Kirkland wrote:
> > According to the 502 servers surveyed, 97.2% use less than 1.5 GB of
> > /tmp.
>
> I'm not expressing any particular view on the overall topic either way
> here, but for the sak
On Fri, Jan 22, 2016 at 09:09:10AM -0600, Dustin Kirkland wrote:
> According to the 502 servers surveyed, 97.2% use less than 1.5 GB of
> /tmp.
I'm not expressing any particular view on the overall topic either way
here, but for the sake of accuracy, I believe that that is not in fact
what the dat
On Thu, Jan 21, 2016 at 5:38 AM, Martin Pitt wrote:
> Dimitri John Ledkov [2016-01-21 11:31 +]:
>> Is it just me, or did the RFC asks about cloud-images alone, and we
>> are diverging to discussing all the things, and all the form factors,
>> and all the installation types.
>
> That's true, so
On Thu, Jan 21, 2016 at 4:14 AM, Martin Pitt wrote:
> Robie Basak [2016-01-21 9:56 +]:
>> I think we need a single canonical (small c) answer. Let's say that I'm
>> an upstream maintainer of a project that currently uses large amounts of
>> space in /tmp (say debdiff on kernel sources, for ex
On Thu, Jan 21, 2016 at 5:31 AM, Dimitri John Ledkov wrote:
> Is it just me, or did the RFC asks about cloud-images alone, and we
> are diverging to discussing all the things, and all the form factors,
> and all the installation types.
>
> Certainly it should be easy to use tmp on tpmfs with cloud
On Thu, Jan 21, 2016 at 11:31:27AM +, Dimitri John Ledkov wrote:
> Is it just me, or did the RFC asks about cloud-images alone, and we
> are diverging to discussing all the things, and all the form factors,
> and all the installation types.
I was making my argument more general, so yes, thanks
Dimitri John Ledkov [2016-01-21 11:31 +]:
> Is it just me, or did the RFC asks about cloud-images alone, and we
> are diverging to discussing all the things, and all the form factors,
> and all the installation types.
That's true, sorry for diverging this.
> And, e.g. imho the default should
Is it just me, or did the RFC asks about cloud-images alone, and we
are diverging to discussing all the things, and all the form factors,
and all the installation types.
Certainly it should be easy to use tmp on tpmfs with cloud-images,
which i would presume would have a cloud-init on/off toggle,
On Thu, Jan 21, 2016 at 11:14:21AM +0100, Martin Pitt wrote:
> Robie Basak [2016-01-21 9:56 +]:
> > I think we need a single canonical (small c) answer. Let's say that I'm
> > an upstream maintainer of a project that currently uses large amounts of
> > space in /tmp (say debdiff on kernel sour
Robie Basak [2016-01-21 9:56 +]:
> I think we need a single canonical (small c) answer. Let's say that I'm
> an upstream maintainer of a project that currently uses large amounts of
> space in /tmp (say debdiff on kernel sources, for example). A user files
> a bug that his machine now explodes
On Thu, Jan 21, 2016 at 03:52:15AM +0100, Dustin Kirkland wrote:
> > What would be the guidance for 1) users; and 2) upstreams; if they want
> > large temporary filesystem space after this change? Would that be to use
> > /var/tmp in all relevant cases? And for upstreams, is this something
> > that
On 21/01/16 02:52, Dustin Kirkland wrote:
> On Wed, Jan 20, 2016 at 5:45 PM, Robie Basak wrote:
>> On Wed, Jan 20, 2016 at 05:27:51AM +0100, Dustin Kirkland wrote:
I'd like to see even some rudimentary experiments done with realistic
workloads before saying this is a better idea than lea
On Wed, Jan 20, 2016 at 5:45 PM, Robie Basak wrote:
> On Wed, Jan 20, 2016 at 05:27:51AM +0100, Dustin Kirkland wrote:
>> > I'd like to see even some rudimentary experiments done with realistic
>> > workloads before saying this is a better idea than leaving things as
>> > they are. We've all specu
On Wed, Jan 20, 2016 at 05:27:51AM +0100, Dustin Kirkland wrote:
> Sure, done! You can find a detailed statistical analysis, as well as
> the raw data for your download and treatment at:
>
> http://blog.dustinkirkland.com/2016/01/data-driven-analysis-tmp-on-tmpfs.html
This is great :) Suddenly t
On 20/01/16 18:39, Dimitri John Ledkov wrote:
> On 13 January 2016 at 12:26, Ben Howard wrote:
>> All,
>>
>> On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
>> rationale, from the bug:
>> * Performance - much faster read/write access to data in /tmp
>> * Security - sensit
On 13 January 2016 at 12:26, Ben Howard wrote:
> All,
>
> On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
> rationale, from the bug:
> * Performance - much faster read/write access to data in /tmp
> * Security - sensitive data would be cleared from memory on boot,
>ra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/01/16 18:53, Steve Langasek wrote:
> On Thu, Jan 14, 2016 at 03:54:30PM +0200, Dustin Kirkland wrote:
>>> As a data point, I used to have my /tmp on tmpfs while I still had a
>>> spinning disk, in order to address the power usage issues of disk
On Wed, Jan 20, 2016 at 05:27:51AM +0100, Dustin Kirkland wrote:
> > I'd like to see even some rudimentary experiments done with realistic
> > workloads before saying this is a better idea than leaving things as
> > they are. We've all speculated and provided anecdotal evidence enough to
> > warran
On Wed, Jan 20, 2016 at 09:17:10AM +0100, Martin Pitt wrote:
> By far the most common reason that I've seen is that files are the
> Unix way for exchanging little pieces of data with other programs,
> like flag files, named pipes, Unix sockets, editors, or in general
> things you need to call exter
Clint Byrum [2016-01-19 23:52 -0800]:
> But that's all nice-to-haves. The real reason I'm still skeptical
> is simply that I don't see /tmp usage being a major factor on cloud
> instances.
FTR, I agree that it is much more desirable on real-iron (the
performance difference with my use cases is *dr
Excerpts from Dustin Kirkland's message of 2016-01-19 20:27:51 -0800:
> On Sat, Jan 16, 2016 at 7:49 PM, Clint Byrum wrote:
> > Excerpts from Dustin Kirkland's message of 2016-01-16 04:25:58 -0800:
> >> On Fri, Jan 15, 2016 at 2:25 AM, Seth Arnold
> >> wrote:
> >> > On Thu, Jan 14, 2016 at 12:27
On Sat, Jan 16, 2016 at 7:49 PM, Clint Byrum wrote:
> Excerpts from Dustin Kirkland's message of 2016-01-16 04:25:58 -0800:
>> On Fri, Jan 15, 2016 at 2:25 AM, Seth Arnold
>> wrote:
>> > On Thu, Jan 14, 2016 at 12:27:58PM +0200, Dustin Kirkland wrote:
>> >> Moreover, just 'sudo apt-get install s
Seth Arnold [2016-01-14 16:25 -0800]:
> The risks and downsides of swapspace feel like a lot compared to the
> slight hassle of having the installer make a swap partition.
I just want to mention that this is far from a "slight hassle". We
managed to screw up the swap partition for many cycles -- a
Excerpts from Dustin Kirkland's message of 2016-01-16 04:25:58 -0800:
> On Fri, Jan 15, 2016 at 2:25 AM, Seth Arnold
> wrote:
> > On Thu, Jan 14, 2016 at 12:27:58PM +0200, Dustin Kirkland wrote:
> >> Moreover, just 'sudo apt-get install swapspace' and watch as swapfiles
> >> are created/deleted a
On Fri, Jan 15, 2016 at 2:25 AM, Seth Arnold wrote:
> On Thu, Jan 14, 2016 at 12:27:58PM +0200, Dustin Kirkland wrote:
>> Moreover, just 'sudo apt-get install swapspace' and watch as swapfiles
>> are created/deleted as needed. If your root disk is lvm-encrypted,
>> then obviously such swap files
On Thu, Jan 14, 2016 at 12:27:58PM +0200, Dustin Kirkland wrote:
> Moreover, just 'sudo apt-get install swapspace' and watch as swapfiles
> are created/deleted as needed. If your root disk is lvm-encrypted,
> then obviously such swap files are encrypted, too.
I've been severely skeptical of the s
On 14 January 2016 at 08:02, Martin Pitt wrote:
>
> Exactly, hence my suggestion to only do it if there is enough RAM.
is it really common for people to spin up cloud instances with more
ram than they expect to use?
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or u
Excerpts from Dustin Kirkland's message of 2016-01-14 02:27:58 -0800:
> On Thu, Jan 14, 2016 at 12:05 AM, Seth Arnold
> wrote:
> > On Wed, Jan 13, 2016 at 11:00:16PM +0100, Martin Pitt wrote:
> >> In a perfect world we'd have some clever tmpfs file system which would
> >> use RAM as available and
On Thu, Jan 14, 2016 at 03:54:30PM +0200, Dustin Kirkland wrote:
> > As a data point, I used to have my /tmp on tmpfs while I still had a
> > spinning disk, in order to address the power usage issues of disk flushing.
> > I found it to be a least-bad option which led to serious degradation of
> > d
On Thu, Jan 14, 2016 at 6:49 AM, Steve Langasek
wrote:
> On Wed, Jan 13, 2016 at 11:00:16PM +0100, Martin Pitt wrote:
>> Ben Howard [2016-01-13 14:26 +0200]:
>> > On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
>> > rationale, from the bug:
>> > * Performance - much faster
On Thu, Jan 14, 2016 at 12:56 PM, Oliver Grawert wrote:
> hi,
> Am Mittwoch, den 13.01.2016, 23:00 +0100 schrieb Martin Pitt:
>> Ben Howard [2016-01-13 14:26 +0200]:
>> > On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
>> > rationale, from the bug:
>> > * Performance - muc
On Thu, Jan 14, 2016 at 1:42 PM, Robie Basak wrote:
> On Thu, Jan 14, 2016 at 01:39:23PM +0200, Dustin Kirkland wrote:
>> +1! MIR swapspace, add it to the images, and get rid of static swap
>> partitions, please :-)
>
> Do we have a blueprint to track the tmpfs /tmp item? MIR swapspace
> should b
On Thu, Jan 14, 2016 at 01:39:23PM +0200, Dustin Kirkland wrote:
> +1! MIR swapspace, add it to the images, and get rid of static swap
> partitions, please :-)
Do we have a blueprint to track the tmpfs /tmp item? MIR swapspace
should be a work item on there in this case.
signature.asc
Descripti
On Thu, Jan 14, 2016 at 1:20 PM, Robie Basak wrote:
> On Thu, Jan 14, 2016 at 12:27:58PM +0200, Dustin Kirkland wrote:
>> Moreover, just 'sudo apt-get install swapspace' and watch as swapfiles
>> are created/deleted as needed. If your root disk is lvm-encrypted,
>> then obviously such swap files
On Thu, Jan 14, 2016 at 12:27:58PM +0200, Dustin Kirkland wrote:
> Moreover, just 'sudo apt-get install swapspace' and watch as swapfiles
> are created/deleted as needed. If your root disk is lvm-encrypted,
> then obviously such swap files are encrypted, too.
I didn't know about this package, tha
hi,
Am Mittwoch, den 13.01.2016, 23:00 +0100 schrieb Martin Pitt:
> Ben Howard [2016-01-13 14:26 +0200]:
> > On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
> > rationale, from the bug:
> > * Performance - much faster read/write access to data in /tmp
> > * Security - sens
On Thu, Jan 14, 2016 at 12:05 AM, Seth Arnold wrote:
> On Wed, Jan 13, 2016 at 11:00:16PM +0100, Martin Pitt wrote:
>> In a perfect world we'd have some clever tmpfs file system which would
>> use RAM as available and start overflowing onto a disk partition
>> (which could be LUKS with a random ke
Seth Arnold [2016-01-13 12:52 -0800]:
> - on m1.tiny and similar sized systems, /tmp will be so small that it may
> well be unusable for what applications expect to do
Exactly, hence my suggestion to only do it if there is enough RAM.
> Whether or not /tmp should be on tmpfs will vary from syst
On Wed, Jan 13, 2016 at 11:00:16PM +0100, Martin Pitt wrote:
> Ben Howard [2016-01-13 14:26 +0200]:
> > On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
> > rationale, from the bug:
> > * Performance - much faster read/write access to data in /tmp
> > * Security - sensitive
On 14 January 2016 at 12:05, Clint Byrum wrote:
> Excerpts from Ben Howard's message of 2016-01-13 04:26:13 -0800:
>> All,
>>
>> On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
>> rationale, from the bug:
>> * Performance - much faster read/write access to data in /tmp
>>
On Wed, Jan 13, 2016 at 02:26:13PM +0200, Ben Howard wrote:
> On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
> rationale, from the bug:
I'm afraid if you make this change you'll get requests to change it back:
- on m1.tiny and similar sized systems, /tmp will be so small
On Wed, Jan 13, 2016 at 11:00:16PM +0100, Martin Pitt wrote:
> In a perfect world we'd have some clever tmpfs file system which would
> use RAM as available and start overflowing onto a disk partition
> (which could be LUKS with a random key) when necessary.. But even
In fact this is what happens,
Quoting Clint Byrum (cl...@ubuntu.com):
> Excerpts from Ben Howard's message of 2016-01-13 04:26:13 -0800:
> > All,
> >
> > On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
> > rationale, from the bug:
> > * Performance - much faster read/write access to data in /tmp
> > *
Quoting Clint Byrum (cl...@ubuntu.com):
> Excerpts from Martin Pitt's message of 2016-01-13 14:00:16 -0800:
> > Ben Howard [2016-01-13 14:26 +0200]:
> > > On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
> > > rationale, from the bug:
> > > * Performance - much faster read/w
Excerpts from Ben Howard's message of 2016-01-13 04:26:13 -0800:
> All,
>
> On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
> rationale, from the bug:
> * Performance - much faster read/write access to data in /tmp
> * Security - sensitive data would be cleared from memor
Excerpts from Martin Pitt's message of 2016-01-13 14:00:16 -0800:
> Ben Howard [2016-01-13 14:26 +0200]:
> > On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
> > rationale, from the bug:
> > * Performance - much faster read/write access to data in /tmp
> > * Security - sens
Ben Howard [2016-01-13 14:26 +0200]:
> On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
> rationale, from the bug:
> * Performance - much faster read/write access to data in /tmp
> * Security - sensitive data would be cleared from memory on boot,
>rather than written (l
Quoting Ben Howard (ben.how...@canonical.com):
> All,
>
> On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
> rationale, from the bug:
> * Performance - much faster read/write access to data in /tmp
> * Security - sensitive data would be cleared from memory on boot,
>ra
All,
On the Ubuntu Cloud Images, we have a request to make /tmp a tmpfs. The
rationale, from the bug:
* Performance - much faster read/write access to data in /tmp
* Security - sensitive data would be cleared from memory on boot,
rather than written (leaked) to disk -- important for encryptio
52 matches
Mail list logo
