# Limits on Collections

**URL:** <https://forum.yugabyte.com/t/limits-on-collections/765>\
**Category:** General\
**Created:** [July 12, 2020, 10:21pm UTC](https://forum.yugabyte.com/t/limits-on-collections/765 "2020-07-12T22:21:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dorian\_yugabyte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/dorian_yugabyte/32/206_2.png) [@dorian\_yugabyte](https://forum.yugabyte.com/u/dorian_yugabyte)\
**Post date:** [July 13, 2020, 10:05am UTC](https://forum.yugabyte.com/t/limits-on-collections/765/2 "2020-07-13T10:05:19Z")

</div>

Hi @llKetanll

- A single row can be up to `64MB` in size.
- You usually want to keep rows maximum in the 1MB - 2MB to have consistent latency.
- Note that big collections are an anti pattern.
- If the application warrants for a bigger number of values, it’s better to model the collection as another table.

The same is true for Cassandra. They support very big collections —\> but they aren’t efficient —\> you should not use them.

Also explained in docs: [Collection data types (MAP, LIST, and SET) [YCQL] | YugabyteDB Docs](https://docs.yugabyte.com/latest/api/ycql/type_collection/#examples)

Regards,  
Dorian  
Technical Support Engineer

---

_[View the full topic](https://forum.yugabyte.com/t/limits-on-collections/765)._