I'm doing a performance audit on a site with a large number of webforms (mid hundreds), and seeing some memory/CPU and i/o overhead from having so many entity bundles.
Some of this can be addressed in Drupal core, e.g. 📌 Optimize field module's hook_entity_bundle_info() implementation Active , however I also realised that webform_submission bundles generally don't have configurable fields at all, the submission data goes into a data base field.
This made me wonder whether webforms definitely need to support dynamic fields - if not it might be able to use a different entity base class or switch that flag to off. And/or whether webform bundles definitely need to be bundles or whether the bundle property could be converted to an entity reference. I realise either of these changes would be potentially major, but wanted to document the question at least - if they definitely need to be bundles and fieldable, then that's more impetus to try to fix as much of this as possible in core.
Active
6.3
Code
It affects performance. It is often combined with the Needs profiling tag.
I am sure people are using custom code or contrib modules to add fields to webform submissions. If we can switch dynamic fields off by default and get a performance gain, that should be okay because people can turn dynamic fields back on as needed.