Mail Archives: geda-user/2015/07/11/10:44:08
On Jul 8, 2015, at 1:20 AM, Gabriel Paubert (paubert AT iram DOT es) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> I find that the netlist generation of my current projects
> (over 20 seconds) is already slow enough.
Generating a full release of my largest project (three boards, ~3500 components, three forms of netlist, three forms of BOM, forward annotated schematics inserted into LaTeX documentation) takes about two minutes. Not enough time to make tea.
> I have the feeling that scheme
> is part of the reason.
For my designs, at least, the gnetlist runs seem to be dominated by the code that searches for net segment connections. That executes before the Scheme back end. It can get very slow if you put a lot of net segments on a single sheet. I try to avoid that for readability anyway. Ales told me years ago that the C code here was inefficient.
It is annoying that this code isn’t controlled by the Scheme back end. It runs whether you need the result or not (as for a BOM). Control of hierarchy expansion is in gnetlistrc (per-project) but I think it makes more sense to have the back end control it. It depends on what kind of netlist you’re making, not on the nature of your project.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -