eflumerf
commented
2 years ago Comment by @jcfreeman2 on 2018-08-20 18:27:35
With commit aedb91a11294b8361a0e5099fca0cb6d0d63070f on the develop branch, this feature is now available, assuming that we have the line advanced_memory_usage: true set in the file referred to by the DAQINTERFACE_SETTINGS environment variable.
This issue has been migrated from https://cdcvs.fnal.gov/redmine/issues/20581 (FNAL account required) Originally created by @jcfreeman2 on 2018-08-10 03:28:21
During bookkeeping, DAQInterface currently sets the max fragment size in the transfer plugins for the eventbuilder's sources table to the same value across all transfer plugins; this max fragment size is set in the file referred to by the DAQINTERFACE_SETTINGS environment variable. As discussed in Redmine Issue 20580, however, different fragment generator types generally have different max fragment sizes, and unnecessary space is wasted if even transfer plugins connecting boardreaders which produce tiny fragments to eventbuilders have their max fragment size set to the largest possible value across _all_boardreaders. It would be good if DAQInterface could perform bookkeeping such that the max fragment size for a transfer plugin reflected the type of fragment generator in the boardreader that transfer plugin connects to an eventbuilder.