Table performance improvement

We have a data table of 150 columns, total 4TB of 90days (each day data like 100Million events). The table has been created with projection group on day, campaign_id and some other common id columns. Many similar processes (like R/Python program and could up to hundreds at same time) are going to pull data from the table mainly on campaign basis (from thousand to million events) through ODBC diver/connection. Question: Is the Vertica table general efficient to handle those pull requests and does it could/need to use some connection pool to improve performance (like pgbouncer: https://www.pgbouncer.org/usage.html and generally: https://stackoverflow.blog/2020/10/14/improve-database-performance-with-connection-pooling/)

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file