The stats_info list used too much memory; when loading a table with 1000
structures and 7 properties, it took about 8 gb, and it scales
quadratically.
We now use a stats_info generator, so the stats are inserted into the
database as soon as they are generated, using a limited amount of
memory.
An incompatible, but arguably cosmetic side effect is that the log
messages are slightly less informative because we don't know how many
rows of stats were generated before we start inserting them.
The stats_info list used too much memory; when loading a table with 1000 structures and 7 properties, it took about 8 gb, and it scales quadratically.
We now use a stats_info generator, so the stats are inserted into the database as soon as they are generated, using a limited amount of memory.
An incompatible, but arguably cosmetic side effect is that the log messages are slightly less informative because we don't know how many rows of stats were generated before we start inserting them.