It runs a full collection, including gen2 (long-lived objects), which can be very expensive. It interferes with the Python GC heuristics.
Was this introduced to address old issues like old leaky behavior of CASA and/or ancient Python versions?
For the pipeline it can cause delays of 10s of seconds or minutes for every task call: CAS-11578, CAS-11690 - serious performance degradation when a CASA-based application does many quick task executions, with lots of blobs of Python objects around (Pipeline context, results, etc.).
Unless there is a good reason to keep this:
I think it should not be carried over to CASA 6.
This is not a feature of CASA 6
I'd experiment with removing it now (CASA 5.5).
CASA Newsletter: deadline for contributions today (+- 2 days). If you have items for the CASA calendar (workshops, meetings, etc), please send them to me by Wednesday.
CASA Docs development server will be for CASA 5.5, not CASA 5.4.1. For documentation that needs to go in CASA 5.4.1: please put info in CASA Docs devel, then email me what should be copied into 5.4.1.
CASA User Survey: 100 completed replies. Interesting detail: majority of users that completed the survey use Ubuntu (see attachment). Article on survey results + helpdesk ticket statistics in CASA Newsletter, full memo is in prep.
added configure check to abort if C++ compiler does not support C++11 STL features
added configure check for GSL version, along with search of complete $PATH
worked on creating a python package closure for publishing binary packages to local PyPi repository
Federico M Pouzols
Friday NAOJ Meeting (9/27/18)
additional validation on CAS-11501 and gave a feedback to the ticket
preliminary workload estimate and ticket assignment for 5.5