Rewriting distrodata.bbclass using tinfoil unfortunately came with a serious performance regression:

1) recipe maintainer test went from a couple of seconds to about a minute;

2) worse, upstream version check (for all recipes) went from about 90 seconds to 12 minutes.

The reason is that each recipe was processed using its own bitbake task; now they're handled in a for loop. I wanted to write a plugin to 'bitbake
-layers' that would show an overview of recipe update status (a replacement for old checkpkg.csv file), but then realized nobody would want to wait for 12 minutes to get it :-(

So it would be great to again be able to parallelize the processing.