This website uses cookies to ensure you get the best experience.
Learn more.
Vector queries compete with transactional work for CPU and memory. What should be measured before choosing a new PostgreSQL compute configuration?
Published
- Query workload, index memory needs, CPU, concurrency, and required latency
- Only the database's creation date
- Only the number of user-interface menus
- Assume adding storage always fixes CPU saturation
Comments — 0
Sign in to comment