Topic: Max Favorite / Set Increase?

I know this is probably unlikely and I'm just barking up the wrong tree, but is there a possibility of getting an increase to the amount of posts that can be in sets and favorites? 10k and 80k respectively is a lot, don't get me wrong, but after being here for quite a while I have accumulated quite a collection of posts that I like. I have been informed that I can use the voting feature to search for my liked posts, but I really like using sets as a form of folders to organize what I like and find it more efficient. If forced to then so be it.
The only reason I have been told as to why there is a limit to them in the first place is because of how they are displayed on someone's profile and yet still don’t quite understand how that works.

Both limits exist because of performance issues, and you can create 75 sets total for 750,000 posts

You can have unlimited upvotes, and you can search with them with voted:me, votedup:me, voteddown:me

overandunder said:
The only reason I have been told as to why there is a limit to them in the first place is because of how they are displayed on someone's profile and yet still don’t quite understand how that works.

It is incredibly expensive to order rows in a table with 1.25 billion rows
Filtering by a user id makes it somewhat cheaper, but it's still relatively expensive to order 80k rows

I am also 100% sure there is more to it than just profiles, for instance /favorites orders by creation date which requires the same ordering as profiles

votes on the other hand can only be ordered by staff, and even then it's only ordered by id which can be further optimized by the database

donovan_dmc said:
Both limits exist because of performance issues, and you can create 75 sets total for 750,000 posts

You can have unlimited upvotes, and you can search with them with voted:me, votedup:me, voteddown:me

Yeah it all makes sense that it all basically boils down to performance. Stinks but ya get what ya can get.

I still just want to know why there isn't any problem with how upvotes are tracked compared to favorites or sets. I unfortunately don't get the technical functionality for this stuff quite like I should.

overandunder said:
I still just want to know why there isn't any problem with how upvotes are tracked compared to favorites or sets. I unfortunately don't get the technical functionality for this stuff quite like I should.

I'm making educated guesses here so take it with a grain of salt
Votes are only ever ordered by the id column, this is the primary column and the database will have leagues of optimizations to make this blazingly fast
On the other had favorites are often filtered by created_at, this is both not the primary column and is a date (this may be an integer internally, I don't know), but either way that will always be slower

We also only have half as many votes as we have favorites
We have 648,468,497 votes
We have 1,253,995,024 favorites

Regardless of anything else operations on the votes table will likely be orders of magnitude faster