Test at your real volume
You are here if Files Connect works, but you haven't tried it at scale. Volume breaks search and listing before anything else. This page tests at yours.
For Salesforce admins, IT and security reviewers, and whoever signs off the budget.
Published by CloudFiles, who sell one of the alternatives once Files Connect stops holding up. Every result here comes from testing at your own volume, not a demo.
Do this now
Build or find a folder the same size as your real one. Run search and listing against it. Write down where it slows or breaks.
Before you start
- You need View Setup and Configuration to open Files Connect config.
- A real-size test set, or a sandbox seeded with realistic volume.
- Time: this is not a five-minute check.
- No admin change required to run the test itself.
How to test it
1. Size it right
Count your actual per-record file volume today: documents per record, and your total corpus size. Don't test against a handful of sample files — that hides the problem this page exists to find.
2. Test listing
Open a record with your real-size folder attached. Time how long the file list takes to render. Note if it degrades, paginates awkwardly, or times out.
3. Test search
Search for a file by name, and by content if supported, inside that same real-size folder. Compare against a small folder to isolate whether volume is the cause.
If your AI is connected to your Salesforce sandbox, ask it directly: “Attach a set of test files representative of our real per-record volume to a test record, then time listing and searching that record's files. Report render time and any errors.”
4. Re-test as you grow
This is not one-and-done. The threshold that breaks today is not the one that breaks after headcount or volume grows further.
What you found
| Typically still works | Typically breaks first | |
|---|---|---|
| Under ~15 files/record | A flat list, read by a person | Nothing, at this size |
| ~15–300 files/record | Search, if you test it directly | A flat list stops working for a person |
| 300+ files/record | — | The CloudFiles widget itself starts to slow, by our own testing |
These are the guide's own thresholds, from deployments. Test your own volume against them rather than assuming they apply.
When to re-test
Whenever your record volume crosses one of these tiers, or after a bulk import or migration.
Where this stops
This page tests whether Files Connect holds up at your volume. It does not decide build versus buy, and it does not scope a migration: the three gates on the guide are where those get answered. CloudFiles sells one of the alternatives once Files Connect doesn't hold up. The test itself needs nothing from us.
Check my working
Most readers will not need this. If the results left you unsure, send them and a person will read them.
- Report: written assessment, two to three working days.
- Reader: a person. Not a bot, not an auto-reply.
- Call: only if you ask. We won't ask twice.
- Fields: four. No phone, no company size, no mailing list.
That's with a person now.
You'll get a written assessment within two to three working days. No call unless you ask for one.