Unloading timeout interval must be configurable through local.conf.

The patch is in review

Alex,

Where we are with this bug, can you check if it's pulled, please mark accordingly

THanks,
Jessica

This is partially working. 

Complete set of patches were reviewed by Richard, who had comments. I amended the patches according to comments and resubmitted. I am waiting for a new review round, will push for one in WW10.

The unloading functionality is missing.

I don't think this is still relevant as Toaster way of running bitbake has changed a lot since this bug is created. Resolving as worksforme.

This isn't about toaster any more. The plan is for bitbake to be able to operate in a memory resident mode. We already have basic functionality for this but we are missing some pieces. One is "autostart" where if the environment is setup in a particular way, bitbake would just automatically go into memory, no messing around with commandline options. The second is some kind of policy on unloading after say an inactivity timer for X minutes.

The biggest blocker on making memory resident bitbake the default is tinfoil2 which Paul is working on. This hasn't been dealt with before now mainly as that piece wasn't ready but it doesn't block this.

Memory resident bitbake should help with various performance and command interaction times, and for example would massively speed up oe-selftest on the autobuilder.

Implementation of autoloading has been sent for review: http://lists.openembedded.org/pipermail/bitbake-devel/2016-July/007727.html

Implementation of auto-unloading has been sent for review: http://lists.openembedded.org/pipermail/bitbake-devel/2016-July/007748.html

Implemented in bitbake 89c6e625d47303b2aad8e6645762f17aee01b2d4.

It's still under review - my second patch is not merged yet.

all changes have been merged into bitbake master