|
|
|
|
|
by morelisp
1359 days ago
|
|
Right, that link covers read units which is also what I expected - essentially the number of files I have to touch - but I still have no clue about write units. Is one block on one non-partitioned non-distributed table one write unit? What about one insert that's two blocks on such a table? What about one block on a null engine with two MVs listening to insert into two non-partitioned non-distributed tables? What if the table is a replacing mergetree, do I incur WUs for compactions? etc. My worry is that it is essentially 1 WU = 1 new part file, which I understand makes sense to bill on but is tremendously intransparent for users - at least I have no clue how often we roll new part files, instead I'm focused on total network and disk i/o performance on one side and client query latency on the other. |
|
For example, I just checked that uploading 1.1GB example table(cell_towers with 14 columns) cost me 0.38 write units.