Hi Team,
We have 2 webforms in our Drupal Portal which consist of approximately 100 fields each.
We had our implementation assessed by a consultancy firm with expertise in Drupal, they have reported that we will be facing scalability problems in our Portal because we expect the number of webform submissions to grow with time(100K+ in a year) and since all the webform submission data gets stored in a single table, it will degrade the performance and scalability limit will come pretty soon.
(100 rows per submission X 100k = 10 million rows in the table)
Hence we are exploring the options if we can store the webform submissions data for each webform into separate tables which should help us improve scalability.
Any suggestions to address this problem will be helpful.
Closed: won't fix
6.1
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I'm curious if anyone has attempted to use MYSQL partitioning on the webform_submission_data table to handle this issue. If you have, I would appreciate hearing about your experience with Drupal's handling of partitioning and the resulting performance improvement.