Having encountered a very large protocol file recently (180k lines, mostly due to SpikeGenerator data), I noticed:
- Loading, and thus startup, is very slow under such circumstances
- The protocol format is extremely redundant and would likely benefit from a better (read: standard & tree-based, e.g. yaml) format both in human readability and loading speed
- SpikeGenerator data should perhaps live in a separate file... or at least on the horizontal axis rather than the vertical one, to ease scrolling to relevant sections if offline troubleshooting is required.
Having encountered a very large protocol file recently (180k lines, mostly due to SpikeGenerator data), I noticed: