-
Notifications
You must be signed in to change notification settings - Fork 65
Open
Description
I use the benchmark.py to test the performance. My local machine ip is 192.168.0.201 and I have another redis-server running on 192.168.0.101. Here is the parameter with the benchmark.py file.
count = 50000
capacity = 1e9
error = 1e-6
Then the benchmark result with 192.168.0.201 is as follows:
Generating 100000 random test words
Generated random test words in 1.082357s
Filter using 20 hash functions and 28755175137 bits
Batch insert : 11.030547s (4532.866814 words / second)
Serial insert: 14.348155s (3484.768594 words / second)
Batch test : 2.664293s (18766.704355 words / second)
Serial test : 5.634645s (8873.673520 words / second)
False positive rate: 0.000000 (0.000001 expected)
Redis set add : 0.119999s (416670.375433 words / second)
Redis pipe chk : 0.884489s (56529.826959 words / second)
Redis pipe sadd: 0.888721s (56260.626908 words / second)
Redis pipe chk : 0.884423s (56534.032935 words / second)
And the benchmark with 192.168.0.101 is as follows:
Generating 100000 random test words
Generated random test words in 1.091547s
Filter using 20 hash functions and 28755175137 bits
Batch insert : 14.148405s (3533.967238 words / second)
Serial insert: 30.745577s (1626.250183 words / second)
Batch test : 6.328274s (7901.048518 words / second)
Serial test : 20.952494s (2386.350744 words / second)
False positive rate: 0.000000 (0.000001 expected)
Redis set add : 0.140992s (354630.235574 words / second)
Redis pipe chk : 0.909973s (54946.676504 words / second)
Redis pipe sadd: 0.906465s (55159.324459 words / second)
Redis pipe chk : 0.887314s (56349.832669 words / second)
It is obvious that the performance result with 192.168.0.101 is much slower than 192.168.0.201.
It seems to be a bug. Any ideas?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels