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
Benchmark against competition #136
Comments
Awesome idea. I use Zola for my blog which comes with elasticlunr. I am evaluating different search solutions. Might want to add Stork to this list as well. |
I found that somebody actually made one that tests a lot of them! https://nextapps-de.github.io/flexsearch/bench/ Unfortunately tinysearch is not in their benchmark list. (neither is pagefind) |
Interesting. We should add it there; also Stork and pagefind. |
one thing I dont see in their benchmark is bandwidth used... so they really should have a second benchmark for that. (that is just as important to me as performance, if they are not interested in making one then I might.) |
How exactly do you define bandwidth? Queries per second? |
no, what i mean is hit the website. perform a search, how many KB had to be downloaded for the search javascript + wasm + index to perform that search. For instance Stork is around 700kb whereas tinysearch is around 100kb for abridge. Obviously the amount of content will affect the index size. In their test they appear to be using Gulliver's Travels they could also benchmark say: 1search, 10searches, etc. to see if that affects the amount of data downloaded to perform the searches, obviously this would affect pagesearch and possibly others because they chunk the index into multiple pieces. |
Gotcha. Yeah, that would indeed be a great comparison. |
People are interested in a size-comparison between
If anyone wants to do a comparison, post a comment here.
Some ideas:
bench
folder and create a pull request. This will make the benchmark reproducible in the future.Feel free to ask questions here before starting.
The text was updated successfully, but these errors were encountered: