Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 25 Oct 2015 11:05:44 -0400
From:      Baho Utot <>
To:        "" <>
Subject:   poudriere
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help
Just a few questions as I am setting this up

# Define to yes to build and stage as a regular user
# Default: no

Any gotchas or ill effects from building as a user?

# By default poudriere uses hw.ncpu to determine the number of builders.
# You can override this default by changing PARALLEL_JOBS here, or
# by specifying the -J flag to bulk/testport.
# Example to define PARALLEL_JOBS to one single job

# How many jobs should be used for preparing the build? These tend to
# be more IO bound and may be worth tweaking. Default: Same as PARALLEL_JOBS

I have a 8 core amd processor does this look sane?

# When building packages, a memory device can be used to speedup the build.
# Only one of MFSSIZE or USE_TMPFS is supported. TMPFS is generally faster
# and will expand to the needed amount of RAM. MFS is a bit slower, but is
# more mature and can have its memory usage capped.

# If set WRKDIRPREFIX will be mdmfs of the given size (mM or gG)

# Use tmpfs(5)
# This can be a space-separated list of options:
# wrkdir    - Use tmpfs(5) for port building WRKDIRPREFIX
# data      - Use tmpfs(5) for poudriere cache/temp build data
# localbase - Use tmpfs(5) for LOCALBASE (installing ports for 
# all       - Run the entire build in memory, including builder jails.
# yes       - Only enables tmpfs(5) for wrkdir
# EXAMPLE: USE_TMPFS="wrkdir data"

# How much memory to limit tmpfs size to for *each builder* in GiB
# (default: none)

# How much memory to limit jail processes to for *each builder*
# in GiB (default: none)

I have 16G of memory should I optimize the above?


Want to link to this message? Use this URL: <>