This blog post is 5 years old! Most likely, its content is outdated. Especially if it's technical.
Now that Autocompeter.com is launched I can publish some preliminary benchmarks of "real" usage. It's all on my MacBook Pro on a local network with a local Redis but it's quite telling that it's pretty fast.
What I did was I started with a completely empty Redis database then I did the following things:
First of all, I bulk load in 1035 "documents" (110Kb of data). This takes about 0.44 seconds consistently!
- GET on the home page (not part of the API and thus quite unimportant in terms of performance)
- GET on a search with a single character ("p") expecting 10 results (e.g.
/v1?d=mydomain&q=p) - GET on a search with a full word ("python") expecting 10 results
- GET on a search with a full word that isn't in the index ("xxxxxxxx") expecting 0 results
- GET on a search with two words ("python", "te") expecting 4 results
- GET on a search with two words that aren't in the index ("xxxxxxx", "yyyyyy") expecting 0 results
In each benchmark I use wrk with 10 connections, lasting 5 seconds, using 5 threads.
And for each round I try with
1 processor, 2 processors and 8 processors (my laptop's max according to runtime.NumCPU()).
I ran it a bunch of times and recorded the last results for each number of processors.
The results are as follows:
Notes
- Every search incurs a write in the form of incrementing a counter.
- Searching on more than one word causes an ZINTERSTORE.
- The home page does a bit more now since this benchmark was made. In particular looking for a secure cookie.
- Perhaps interally Redis could get faster if you run the benchmarks repeatedly after
the bulk load so it's internals could "warm up".
- I used a pool of 100 Redis connections.
- I honestly don't know if 10 connections, 5 seconds, 5 threads is an ideal test :)
Basically, this is a benchmark of Redis more so than Go but it's quite telling that running it in multiple processors does help.
If you're curious, the benchmark code is here and I'm sure there's things one can do to speed it up even more. It's just interesting that it's so freakin' fast out of the box!
In particular I'm very pleased with the fact that it takes less than half a second to bulk load in over 1,000 documents.
- Previous:
- Match the whole word in auto complete maybe 10 April 2015
- Next:
- AngularJS $q notify and resolve as a local GET proxy 18 April 2015
- Related by category:
- Go vs. Python 24 October 2014 Go
- My favorite Go multiplexer 28 January 2015 Go
-
Unzip benchmark on AWS EC2 c3.large vs c4.large 29 November 2017 Go
- How to slice a rune in Go 16 March 2015 Go
- Autocompeter is Dead. Long live Autocompeter! 09 January 2017 Go
- Related by keyword:
- Fastest way to uniqify a list in Python 14 August 2006
- Django ORM optimization story on selecting the least possible 22 February 2019
-
How to do performance micro benchmarks in Python 24 June 2017
- The ideal number of workers in Jest 08 October 2018
- Benchmark compare Highlight.js vs. Prism 19 May 2020
