Closed mariusves closed 7 years ago
So far, the whole PQ-set is imported first and afterwards the uneeded part of the array is being deleted. This can lead to very long loading times and (temporarily) high memory usage.
Therefore, the slicing of the PQ-array shall be performed prior or during the importing process using sqlalchemy. See: http://docs.sqlalchemy.org/en/rel_0_9/dialects/postgresql.html#sqlalchemy.dialects.postgresql.ARRAY
Added a first improvement of the PQ slicer, reduced loading times significantly.
Closed, since so far no further improvement is needed.
So far, the whole PQ-set is imported first and afterwards the uneeded part of the array is being deleted. This can lead to very long loading times and (temporarily) high memory usage.
Therefore, the slicing of the PQ-array shall be performed prior or during the importing process using sqlalchemy. See: http://docs.sqlalchemy.org/en/rel_0_9/dialects/postgresql.html#sqlalchemy.dialects.postgresql.ARRAY