100,000 rows is pretty small. Import your data to your cluster, do a nodetool flush on each node, then you can see how much disk space is actually used.
There are different compression tools available to you when you create the table. It also matters if the rows are in separate partitions or you have many rows per partition. In one exercise I have done, individual partitions can cause the data to expand from 0.3 MB (with many rows per partition) to 20 MB (one row per partition) – all from the same data set. Your compaction settings can also change the size of data on disk. Bottom line – precise math requires more parameters than you have given. Actual experimentation is easier. Sean Durity From: lampahome <pahome.c...@mirlab.org> Sent: Wednesday, January 1, 2020 8:33 PM To: user@cassandra.apache.org Subject: [EXTERNAL] Re: How bottom of cassandra save data efficiently? Dipan Shah <dipan....@hotmail.com<mailto:dipan....@hotmail.com>> 於 2019年12月31日 週二 下午5:34寫道： Hello lampahome, Data will be compressed but you will also have to account for the replication factor that you will be using. Thanks, Dipan Shah The key factor about efficiency is replication factor. Are there other factors? ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
