mnoGoSearch search engine supports HTTP compression (Content encoding). Compression can have a major impact on the performance of HTTP transactions. The only way to obtain higher performance is to reduce the number of bytes transmitted.
Using content encoding to receive server response alows to reduce traffic twice or more.
The HTTP 1.1 (RFC 2616) specification contains four content encoding methods: gzip, deflate, compress, and identity.
When Content-encoding is enabled, mnoGoSearch indexer sends to a server Accept-Encoding: gzip string in HTTP headers.
If the server supports gzip encoding, it sends gzip encoded response.
To compile mnoGoSearch with HTTP Content encoding support, zlib library is required.
To enable HTTP Content encoding support, configure mnoGoSearch with the following option:
./configure --with-zlib
Use this option along with all the other necessary ones.
Current version of mnoGoSearch 3.2 support only gzip, deflate and compress compression methods. It is planned to implement identity encoding support in future versions of mnoGoSearch.