Re: poudriere-devel and tmpfs use by inactive builders: an example

Hello.

When jobid03 is running and jobid06 has finished its work and is on standby, the environment of jobid06 remains intact, which means that tmpfs continues to use memory.
When looking inside /usr/local/poudriere/data/.m/main-CA76-default/06/var/db/pkg/local.sqlite, all the packages installed as dependencies of the last built port remain installed, and if llvm19 are installed, it seems to consume as much as 2GB.

...isn't it right?

Regards.

On 2026/04/30 12:22, Mark Millard wrote:
> # poudriere version
> poudriere-git-3.4.99.20260425
> 
> The following is an extraction of tmpfs lines from a df -m ouptput in a
> UFS system context. The only active builder was 03 . All other future
> builders were waiting for 03 to finish because they were dependent on
> 03's results.
> 
> 1M-
> blocks   Used  Avail Capacity  Mounted on
> 131780   2329 129451     2%
> /usr/local/poudriere/data/.m/main-CA76-default/03
> 131442   1991 129451     2%
> /usr/local/poudriere/data/.m/main-CA76-default/03/usr/local
> 131334   1883 129451     1%
> /usr/local/poudriere/data/.m/main-CA76-default/06/usr/local
> 131144   1693 129451     1%

(omit)(omit)

> The total of the non-03 tmpfs space used: 1991+. . .+97 == 14184
> So: approx.= 13.85 GiBy†es.
> 
>