Hi, I basically just have a question. We're potentially going to be setting up a 17 field Webform that could receive up to 300K submissions a week (which boils down to, say, about 1700 an hour - a lot more during spikes). Assuming we have the appropriate hardware environment and system architecture in place (massive), do you envision other potential performance problems with Webform? For example, would exporting results from that many submissions take up so much memory that it will never work? Would the form submissions take so much processing that other website performance would suffer? Is there a way to offload Webform tables to a separate database? Are there are other tips and hints you could offer that might keep us from regretting to go this route (vs. building a custom form)? Any help/suggestions you can provide, even a couple sentences, would be greatly appreciated!

Thanks,
Mike

Comments

quicksketch’s picture

quicksketch
he/him
commented

At that sort of volume you might consider a custom module, because Webform's database storage probably would not scale to that size. Right now Webform only uses a single table for its data storage, for *all* webforms on the site. It creates a row for every field within every submission, meaning a single submission might take up 20+ rows within the table. Combine that with several hundred webform nodes over the course of the year, and again with 300,000 submissions a week, you end up with: 20 (estimate) * 300,000 * 54 = 312 million rows in that single database table. Whereas if you made a separate table per form (which I think may be necessary in your situation), then you'd only have 20 * 300,000 rows per table, or ideally you'd make every submission a single row.

So basically I don't think Webform would be a good solution for you, if you're handling that sort of traffic you'll likely need a more optimized solution.

mmorris’s picture

mmorris commented

quicksketch,

Thanks so much, this is exactly the kind of info I was looking for.

Cheers,
Mike

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Closed (fixed)