Manticore 2.7.5 vs Sphinx 3.1.1


Here we benchmarked Sphinx 3.0.2 vs Manticore 2.6.2. This was 8 months ago and both Manticore and Sphinx changed since then. As it’s said in Sphinx 3.0.3 announcement Sphinx 3.0.3 is up to 2x faster compared to 3.0.2, so it’s interesting to do another benchmark. This time let’s test on a real dataset – Hacker News comments.

The benchmark was conducted with the following conditions:


Sphinx UDF example


Many databases and search engines allow you to customize your queries using your own so called “user defined functions” or UDF. Sphinx and Manticore are not exceptions. There’s a long section in documentation about this –

Here I want to give just a quick example of how you can make a UDF which enables some fucntionality which can be really useful in some cases, but missing out of the box – sleep() function.


Scripting in config

Did you know that Sphinx and Manticore Search configs allow you to do scripting by using shebang syntax? Here is an example of how useful it can be in some cases:

Imagine you have 3 tables with identical structure that you would like to index into 3 indexes one per table. You can just make a php script which will do it and use it as a Manticore Search config instead of describing each source/index separately:

Research on Jemalloc

As said on

jemalloc is a general purpose malloc(3) implementation that emphasizes fragmentation avoidance and scalable concurrency support.

Some Sphinx and Manticore Search users prefer jemalloc over malloc and say it allows to save some RAM. I’ve tested how jemalloc affects resource consumption and response time for 2 weeks on 3 Manticore clusters (se03/03-2, se04/04-2, se05/05-2) each of which:


© 2019 Manticore Software Ltd. Registered Address: Office 2, Derby House, 123 Watling Street, Gillingham, Kent, ME7 2YY
Company No. 10772872