#2195 closed complaint (duplicate)
[PROPOSAL] Long table generation times.
Reported by: | Alex Olivas | Owned by: | Jan Soedingrekso |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | combo simulation | Keywords: | |
Cc: |
Description
This is on the latest trunk. The table builds are *much* longer than they used to be.
Change History (3)
comment:1 in reply to: ↑ description Changed 6 years ago by Jan Soedingrekso
comment:2 Changed 6 years ago by Alex Olivas
- Resolution set to duplicate
- Status changed from new to closed
Closing this a 'duplicate' since the real fix is to move these to a production data location (separate from test data).
comment:3 Changed 5 years ago by Alex Olivas
- Milestone Autumnal Equinox 2018 deleted
Milestone Autumnal Equinox 2018 deleted
Note: See
TracTickets for help on using
tickets.
Replying to olivas:
They are now in a new structure and not that compact, so every time something slightly changes, not everything is build new.
Also the tables can be written in a binary or human readable way, which can be adapted in the config file.
I think it is ok, that the tables need more time to write, because they’re just written once.
However, they should be stored in $I3TESTDATA, so that not every one needs to build them but I have no permission to write them there.
How much longer do they need to create?