Load Test FWSS

[BigLep]

Done Criteria

A "load test" is conducted against the FOC GA product to help flush out any reliability bugs.

It's important that each of the concurrent "users"

• not share a dataset
• upload a unique file (so IPNI doesn't have any previous providers for the file)
• verify that all the expected links are accessible (e.g., proofs link, /piece download link, /ipfs download link). This presumably means we didn't have any errors.

At the minimum, we want to be able to support 100 concurrent datasets being created.

Why Important

Identify easily discoverable reliability issues that would manifest when we do official announcements about FOC being GA.

Notes

1. A round of this was done in 202511 in Load test filecoin-pin-website filecoin-project/filecoin-pin-website#103 . Scripts can be used from there (see [WIP] chore: saving load-test scripts in draft PR filecoin-project/filecoin-pin#228 )
2. Load testing to some degree was happening as part of debugging and validating Investigation Ticket: PDP Piece Lookup Timeout on Calibration Network #380 (example)
3. It would be ideal if there is a way to filter sentry traces to the requests related to this load test so we can report on its success.

[BigLep]

A load test on a single SP onboarding and its continued proving has been documented in filecoin-project/curio#892

[BigLep]

I reduced estimate to 1 ideal dev day (from 2) as I'm assuming 2 ideal dev days for filecoin-project/curio#892 which will be useful for this issue as well.

[BigLep]

Bumping this back to M4.2 since the mainnnet readiness load testing is happening in filecoin-project/curio#892 . We'll determine after M4.1 if more load testing is needed.