Application should perform well with 150 concurrent users and over 100,000 rows of data

[lbeaufort]

Business Reason

For an alpha release, we should reliably handle 150 concurrent users. Peak FECFile usage could be over 5,000 concurrent users

As a [role], I will be able to [blank] so that I can [business reason]

Acceptance Criteria

If [precedent] When [action] Then [result]

Dev notes

Current average response time for 150 concurrent users is over 3 seconds (3,000-4,000ms), and that's just for read queries, not for writes. Also, there's very little data in the system. Ideally, that should be under 500ms with over 100,000 rows of data

Results from running 3 application instances, 1.5GB

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-210