13 comments

[ 2.6 ms ] story [ 27.5 ms ] thread
Will it be compatible with incoming 1.8 version of haProxy ? With the http2 ?

Is there a way, like in varnish, to purge some URL ?

If yes, I would love to give it a try !

Current nuster is based on haproxy-1.7.9.

nuster based on haproxy-1.8 is WIP, and will be released when haproxy-1.8 release(not rc).

Also purging URL is not ready yet, its under development with other features like cache stats, admin throught web/api, shared memory in multiple processes.

Ah too bad. I've got Magento behind my Varnish (with nginx for serving). They have native Varnish management, but I would have adapted it for using your tool. Well, I'll wait ´til it's ready :)
so how would something like this work if i'm already using an apache2 server?
Given that HAProxy 1.8 adds a small object cache, what does this do etra?
Yeah, I just noticed that. The cache functionality introduced in HAProxy 1.8, as it said, small object cache, which means that only small response can be cached, which defaults to 16KB as defined by the global parameter `tune.bufsize`.

There is no such limitation in nuster, and nuster can do more things like cache based on request url/query/header/cookie, response headers, request rate, TTL, etc.

Why forking, btw? Curious why you chose that route.
I'm releasing initial version, and plan to collaborate the developing of all functionalities I want on Github, then I'll send the patch to the HAProxy team.
Both nginx and varnish make a big deal about their performance. What design choices is it that makes haproxy and/or nuster so much faster?
I'm updating benchmark report right now, will share once done. Also the technical details
Perhaps add Apache Traffic Server for completeness!
(comment deleted)
I meant in terms of lower amount of syscalls per request or whatever it may be. What’s the magic sauce made of?! :-)