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

[pdq][mlh] Add querying benchmark to /bin #1697

Open
Dcallies opened this issue Nov 13, 2024 · 0 comments · May be fixed by #1699
Open

[pdq][mlh] Add querying benchmark to /bin #1697

Dcallies opened this issue Nov 13, 2024 · 0 comments · May be fixed by #1699
Labels
mlh Related to Major League Hacking Fellowship pdq Items related to the pdq libraries or reference implementations

Comments

@Dcallies
Copy link
Contributor

Similar to #1696 , we want to add a tool to help us benchmark query lookup speeds.

The script should by default randomly generate PDQ hashes from noise.

At a minimum it should contains:

  1. -q: The number of queries to run (default 1000 or something)
  2. -b: The number of PDQ hashes to query against (default 10000 or so)
  3. -d: What distance to use as a match (default 31)
  4. --seed: A seed for the random number generator
  5. -m: Method (default to brute force linear scan). This is the only method we will start with.

It should output:

  1. Total time querying (if -b is very large, it can take up significant time, so make sure to only start the timer afterwards)
  2. Time per query

In followups, we will add more methods like faiss, faiss_gpu, etc.

@Dcallies Dcallies added pdq Items related to the pdq libraries or reference implementations mlh Related to Major League Hacking Fellowship labels Nov 13, 2024
@16BitNarwhal 16BitNarwhal linked a pull request Nov 29, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mlh Related to Major League Hacking Fellowship pdq Items related to the pdq libraries or reference implementations
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant