It’s hard to say. It’s probably best to test both scenarii and see which one provides the best performance. Taking into account that for a lot of data, you can also use high scaling tables (Glide Big Tables, SQL).
In general, I would make sure that the database is clearly structured: if you have object A and object B, better create 2 tables and create a relation between the table than start putting all objects in the same table.
Make sure tables are normalized.
There is a thread from a while back where someone explained that when a table becomes too big, it can be better to break up the table. This practice had a specific term, but I cannot remember the term nor can I locate the topic.