find upper boundaries for collections. UI and API should be considered separately, as 1 million users may not be an issue for backend, but maybe the UI would barf.
we should find the extreme upper bounds, and also find where the highest number is where we are confident in a stable state with those numbers. for instance, 100k users in a list has been found technically to work, but maybe we'd set the limit at 20k as the highest we officially support.
we ought to put guardrails in at those max points, not much stopping someone from creating issues today with large designs
- participant list sizes
- number of decision points
- number of conditions
- size of text values
- other things
find upper boundaries for collections. UI and API should be considered separately, as 1 million users may not be an issue for backend, but maybe the UI would barf.
we should find the extreme upper bounds, and also find where the highest number is where we are confident in a stable state with those numbers. for instance, 100k users in a list has been found technically to work, but maybe we'd set the limit at 20k as the highest we officially support.
we ought to put guardrails in at those max points, not much stopping someone from creating issues today with large designs