Bug #10983
project summary for large projects requires excessive amounts of memory
Start date:
11/23/2015
Due date:
% Done:
100%
Estimated time:
Description
Large projects require large amounts of memory to get the project summary. For example, "samweb -e mu2e project-summary mu2epro_sim.mu2e.cd3-cosmic-g4s1-target1.0715a.art_prestage_20151120094848" won't run with the vmem limited to 4GB (my dev server can't safely allow more than that). This is presumably a consequence of using the ORM: the query needs to be rewritten to use a named cursor so it doesn't have to build up the entire result set at once.
Associated revisions
History
#1 Updated by Robert Illingworth over 4 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset 9847fb9989d1bb1a4f3488b402f810bae7018da6.
#2 Updated by Robert Illingworth over 4 years ago
- Status changed from Resolved to Closed
Lower memory (and maybe faster) method of getting project summary info (resolves #10983)