Please take this survey to help us learn more about how you use third party tools. Your input is greatly appreciated!
Eon Mode - Performance if data is not in the Depot and policy to rehydrate
I imagine that performance will be compromised if the data queried is not in the Depot - is this correct?
What is the policy to rehydrate the Depot?
Question from Eon Mode: Past, Present, Future
Leave a Comment
Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.
If the data queried is in the depot, especially for I/O bound queries, the performance is better than querying against communal storage location(when data is not in the depot). We have observed 2-3 times faster when comparing querying against depot vs. querying against communal storage for certain types of queries, this depends on data volume and query types, for other workloads, there might be more performance benefits if the data queried is in Depot.
There are some scenarios that depot can be re-hydrated:
Hope this help, please feel free to let us know if you have further questions.
2 - 3 x slower?
Is this valid only for AWS (S3) deployment?
I expect in case of Pure storage the degradation is negligible.
Do you have any numbers for setup with Minio storage?
In depot query performance is always going to better than communal storage in all Eon deployments cloud and in premise. Differences always depends on complexity of query and amount of data processed. Depot plays key role as performance booster for all Eon deployments and we recommend customers to take advantage of depot that is on local attached storage.