Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Search Documentation | 2025.6

# Index throughput

The throughput of P4 Search depends on the size of your deployment and the types of files you have.

The following table displays the number of files indexed per minute for typical configurations of P4 Search and its services in a medium site deployment.

To learn more about deployment sizes, see System requirements.

Files | Throughput (files/min) | P4 Search configuration | Elasticsearch configuration | DeepDetect1 configuration | P4 Render2 configuration
--- | --- | --- | --- | --- | ---
Text < 30GB total file size < 3,000,000 files | 8000 | 12 CPUs 32GB RAM | 4 CPUs at low utilization 32GB RAM | N/A | N/A
Images < 30GB total file size < 100,000 files | 700 | 16 CPUs 32GB RAM | 4 CPUs 32GB RAM | N/A | N/A
Images with AI tagging < 30GB total file size < 100,000 files | 50 | 4 CPUs 32GB RAM | 4 CPUs 32GB RAM | 64 CPUs 48GB RAM | N/A
3D assets < 900GB total file size < 20,000 files | 80 | 10 CPUs 32GB RAM | 4 CPUs 32GB RAM | N/A | 16 instances 64 CPUs 64GB RAM

1. DeepDetect is used for AI tagging.

2. P4 Render is used for 3D rendering.

Your search for returned results