Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to get_random_community_id: add filters for nsfw and private, use algorthm that doesn't scan the entire table #5267

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

dullbananas
Copy link
Collaborator

No description provided.

@dullbananas dullbananas marked this pull request as ready for review December 21, 2024 00:39
CREATE INDEX idx_community_random_number ON community (random_number) INCLUDE (local, nsfw)
WHERE
NOT (deleted OR removed OR visibility = 'Private');

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why smallint? due to birthday paradox you have a high collision probability already with 2^(n/2) communities = 2^8 = 256 communities

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It uses less space, and collisions are fine because the random number is updated after the community is picked

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why would you update the number after picking?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its described here. I'm sure there are others ways of doing it, allowing collisions and updating the random number after picking, being one way to do it.

Copy link
Collaborator

@phiresky phiresky Dec 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right, i missed the last paragraph there. Still seems a bit awkward to me, especially having a read-only innocuous request cause a table write.

Why don't you just do select * from community where id = 1+(random() * (select max(id) from community))::int in a loop? The id of communities is already unique and uniformly distributed, with a fill rate of like 99% (so needing more than one/two queries is exceedingly unlikely) - no new column or modifying query or function needed.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess that would make filtered (nswf/local) more difficult, mh.

CREATE INDEX idx_community_random_number ON community (random_number) INCLUDE (local, nsfw)
WHERE
NOT (deleted OR removed OR visibility = 'Private');

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its described here. I'm sure there are others ways of doing it, allowing collisions and updating the random number after picking, being one way to do it.

crates/db_schema/src/impls/community.rs Show resolved Hide resolved
@dessalines dessalines requested a review from phiresky December 27, 2024 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants