LArSoft

The good design of data product classes is capital for the performance of art.
Among the things to be checked:
- presence of dummy copy and move constructor, assignment operators and destructors: the presence of a destructor should, and the presence of a copy or move constructor or operator will, stop the compiler from generating automatic code for moving data. This will impact the performance in places where a move could occur and instead a copy will be used
- large structures at default construction level for data products will have a bad impact; a data product is what is put in the event (edm::Event::put), and since we most often use @std::vector@s we should be safe from this point of view
- large structures anywhere in the data products have a dramatic impact the memory and speed