Usage of /tmp on Solaris buildfarm

[Chuck Atkins]

Hi Dago,

I moved the builds to run out of /tmp a while ago because it seemed to
speed them up significantly by doing so.  I haven't looked at them in quite
some time though as they've been working well.  There were many moving
parts at the time and it's possible one of the other changes I made to the
automation is responsible for the speed up (like shifting the start time to
run when the machine is less loaded).  I'll take a look at them tomorrow
and try running them out of home is instead to stay tidy.  IIRC the
performance was a problem only on the Solaris 10 machine so I should be
able to move all the Solaris 11 builds without issue.  Best case scenario
it will have little impact on build times.  Worst case scenario the Solaris
10 builds are significantly slower out of home and I just reduce the number
of builds running to focus on the most significant instead of trying to run
all possible combinations.

Thanks for the heads up.  I'll clean it up.

- Chuck




On Thu, Jun 20, 2019, 16:03 Dagobert Michelsen <dam at opencsw.org> wrote:

> Hi Chuck,
>
> we noticed that you store a lot of stuff in /tmp. This is discouraged in
> Solaris as /tmp
> is a memory filesystem - files there directly occupy RAM which is then
> missing from
> file system cache making the whole system unusable slow. Please do not
> store stuff there,
> if you need more space I can increase your quota. Your regular home is on
> ZFS with lazy write
> enabled, so writing to /tmp should also not be faster than writing to your
> home directory.
>
>
> Best regards
>
>   — Dago
>
> --
> "You don't become great by trying to be great, you become great by wanting
> to do something,
> and then doing it so hard that you become great in the process." - xkcd
> #896
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/buildfarm/attachments/20190620/51bf4ccb/attachment.html>