dc_tuple_mover_events / storage containers

1) it is number of ros containers per projection
2) in simple terms it is set or rows
3) yes it is expected

Vertica will not be able to handle flood of small transactions, you will get problems from all sides.

@Sergey_Cherepan_1: Yes, we know that Vertica is not optimized for small transactions. However, we have a specific use case in our environment that could lead to such a scenario, and with the tests we want to find the thresholds where something goes wrong so we can define the boundaries there (and hopefully avoid/block them programmatically ).

@SruthiA Thnx for your answers.
Rgd 2): Could you explain this perhaps a little bit more?
Rgd 3): So does this mean that container_count shows the current number of ROS and not the number when the specific event was recorded?

2) storage container a broad term. in vertica, there are 2 types : WOS and ROS. vertica is internally organized into a hybrid store consisting of two distinct storage structures. The Write-Optimized Store (WOS) container is a data structure that generally fits into main memory and is designed to efficiently support insert and update operations. Conversely, the Read-Optimized Store (ROS) container is a set of rows stored in a particular group of files and is both sorted and compressed, making it efficient to read and query one or more Projections. If you are interested to know more about vertica architecture, please go through the below white paper.

https://docs.media.bitpipe.com/io_10x/io_102056/item_467954/The Vertica Analytic Platform Technical Overview White Paper.pdf

3) it means that particular txn merged that many ros containers.

@SruthiA Thnx for the answers, but WOS was removed with Vertica 10.

@kfu : Yes. WOS was removed in vertica 10. I was trying to explain what is storage container.