artiq-full evaluation is a memory hog #25
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Slow and makes hydra-eval-job use more than 20GB and sometimes crash with OOM.
Does
8f7308b
improve the situation?A migen patch may not be the most durable. I'm open for suggestions.
It's the evaluation (i.e. hydra-eval-job process, as I mentioned) that is the problem. Not the Vivado runs, where you actually want the little parallelism it supports to reduce build time.
This improves memory usage and duration a lot for me:
f1325dce29
Thanks, also much better on nixbld.m-labs.hk.
I'm curious what was happening - lots of copies of the entire nixpkgs object?
For each of the board jobs, it was loading and evaluating the Vivado, Artiq and associated declarations over and over. I think it's putting
import
statements inside much-called functions (artiq-board
) even when none of the function parameters are actually passed along.