* OE and SSDs
@ 2014-02-13 10:38 Carlos Rafael Giani
2014-02-13 17:00 ` Philip Balister
0 siblings, 1 reply; 3+ messages in thread
From: Carlos Rafael Giani @ 2014-02-13 10:38 UTC (permalink / raw)
To: openembedded-devel
Hello,
we are considering purchasing SSDs for our development machines, for
faster I/O and better latency. One open question is whether to buy TLC-
or MLC-based drives. TLCs are considerably cheaper. They would not be
used in build bots, but on the other hand, people will build entire
images with OE by themselves during development.
So I wonder about the impact on the drive's lifespan, and whether or not
it is severe enough to warrant the more expensive MLC drives (up to 2
times more expensive).
Did anybody made experiences with these? Any recommendations?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: OE and SSDs
2014-02-13 10:38 OE and SSDs Carlos Rafael Giani
@ 2014-02-13 17:00 ` Philip Balister
2014-02-14 12:46 ` Sander van Grieken
0 siblings, 1 reply; 3+ messages in thread
From: Philip Balister @ 2014-02-13 17:00 UTC (permalink / raw)
To: openembedded-devel
On 02/13/2014 05:38 AM, Carlos Rafael Giani wrote:
> Hello,
>
> we are considering purchasing SSDs for our development machines, for
> faster I/O and better latency. One open question is whether to buy TLC-
> or MLC-based drives. TLCs are considerably cheaper. They would not be
> used in build bots, but on the other hand, people will build entire
> images with OE by themselves during development.
>
> So I wonder about the impact on the drive's lifespan, and whether or not
> it is severe enough to warrant the more expensive MLC drives (up to 2
> times more expensive).
>
> Did anybody made experiences with these? Any recommendations?
A lot of people use as much ram as they can fit in the box and use
tmpfs'. You might try that approach first.
Philip
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: OE and SSDs
2014-02-13 17:00 ` Philip Balister
@ 2014-02-14 12:46 ` Sander van Grieken
0 siblings, 0 replies; 3+ messages in thread
From: Sander van Grieken @ 2014-02-14 12:46 UTC (permalink / raw)
To: openembedded-devel
On Thursday, February 13, 2014 18:00 CET, Philip Balister <philip@balister.org> wrote:
> On 02/13/2014 05:38 AM, Carlos Rafael Giani wrote:
> > Hello,
> >
> > we are considering purchasing SSDs for our development machines, for
> > faster I/O and better latency. One open question is whether to buy TLC-
> > or MLC-based drives. TLCs are considerably cheaper. They would not be
> > used in build bots, but on the other hand, people will build entire
> > images with OE by themselves during development.
> >
> > So I wonder about the impact on the drive's lifespan, and whether or not
> > it is severe enough to warrant the more expensive MLC drives (up to 2
> > times more expensive).
> >
> > Did anybody made experiences with these? Any recommendations?
>
> A lot of people use as much ram as they can fit in the box and use
> tmpfs'. You might try that approach first.
It might be interesting to in some way integrate this behaviour automatically, if an FS-on-SSD is detected and plenty of RAM is present. For instance, if INHERIT+="rm_work" is set, the build directory could be automatically overlayed using aufs/unionfs, since the intermediate result in the build directory is then by definition irrelevant after a succesful build.
I have no idea though, what the minimum amount of free memory would need to be to be sure that none of the bigger builds fail.
Regards,
Sander
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-02-14 12:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-13 10:38 OE and SSDs Carlos Rafael Giani
2014-02-13 17:00 ` Philip Balister
2014-02-14 12:46 ` Sander van Grieken
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.