How does planned concurrency set to AUTO affect query optimization with resource pools? Do you recommend it?
Question from Optimizing Query Performance and Resource Pool Tuning @rbankula @bat
AUTO means it will take the value of the number of cores on your system. It's no different than hardcoding a number unless your hardware changes.
As for recommending it, I strongly recommend you read up on Query Budgets and set up your MaxMemorySize and PlannedConcurrency values appropriately (I tend to leave the MemorySize unused so as not to reserve memory for a resource pool that then is unavailable to the general pool). More often than not, you are going to want to put an actual value there, and not AUTO.
Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.