I understand the basic definition of a "hot partition" to be a partition that receives a lot of reads and writes, usually due to poor data modeling.
What is considered to be "a lot" in terms of how frequently that partition receives read or write requests? Would it need to be on the order of several transactions per second?
Also, what is a bigger performance problem: a read-heavy or write-heavy workload? I know Cassandra is generally more optimized for writes, but I read recently that 3.11 has better read performance than previous versions.
Thanks so much for any insight you can provide!