Performance and large collections
Understand how PMA keeps large collections responsive, why the newest organization-wide history loads first, and how deeper animal history remains available on demand.
Before you begin
- Use a current supported browser and a stable connection for initial synchronization.
- Open the correct PMA organization before reviewing counts or history.
- Allow an individual animal profile to finish loading before printing a complete report.
Interface walkthrough
These annotated interface maps describe the current PMA controls. They do not replace a real record review in your workspace.
PMA loads a bounded recent timeline during startup so every screen does not download the entire lifetime history.
Opening an animal profile or report requests that animal’s deeper history separately, up to the current safety boundary.
Recent data remains usable while deeper history loads; a warning appears if the deeper request fails.
Authorized operators can review database size, table pressure, index readiness, and anonymous statement timing without seeing customer content or SQL text.
Step-by-step workflow
Search before browsing a very large collection
Use animal search and filters to narrow the working set instead of scrolling through every record.
Open the individual animal for complete context
The profile requests deeper animal-specific history after the core identity and recent records are available.
Wait for the report loading notice to clear
Before printing or saving a long animal report, confirm that deeper husbandry history has finished loading.
Report repeated slowdowns
Record the route, approximate time, collection size, device, and connection type. Do not include passwords, recovery codes, or secret keys.
Expected result
Large organizations can enter and navigate PMA without every route downloading the full husbandry history, while detailed animal records remain available when needed.
Safety boundaries
- Beta 88 never creates synthetic performance records in Production.
- Scale fixtures require an explicit isolated organization named PMA Scale Lab — Beta 88.
- Performance diagnostics expose numeric catalog evidence only, not customer records or raw SQL text.
- Pagination and bounded loading must never delete, archive, or rewrite historical records.
Troubleshooting
The profile says deeper history could not be loaded
Recent records are still available. Check the connection, refresh the profile, and retry before producing a complete report.
An older event is not in an organization-wide screen
Open the associated animal profile. Organization-wide startup history is intentionally bounded, while animal-specific history loads separately.
A large report still feels slow
Confirm the loading notice clears, reduce other active browser tabs, and report the animal’s approximate event count and device type.