Rehydration latency limits for Datadog Logs Archive

The goal is to understand the upper bound of latency between the completion of a Datadog Logs rehydration job and the moment the rehydrated logs become searchable in the platform.

Datadog documents that rehydrated logs become searchable after the job finishes, but the exact latency is not guaranteed and can vary with backend load, data volume, and the number of concurrent rehydration jobs, which are limited to five per organization. Additionally, rehydrated logs count toward log ingestion limits, which may affect billing if large volumes are processed frequently.

What is the typical latency range for a 1 GB rehydration job under average load? Does latency increase proportionally with data volume? How does running the maximum of five concurrent rehydration jobs affect latency?