Nginx HTTP Push Module

#1

Post by stephencelis » Thu, Nov 19, 2009, 1:40 PM UTC

Nginx HTTP Push Module
pushmodule.slact.net

Re: Nginx HTTP Push Module

#2

Post by thijsterlouw » Thu, Nov 19, 2009, 2:58 PM UTC

did anyone already do performance tests? I'm especially interested in memory and cpu usage. Any limitations?

Re: Nginx HTTP Push Module

#3

Post by danfitch » Thu, Nov 19, 2009, 3:29 PM UTC

Site isn't working for me, but the github url is http://github.com/slact/nginx_http_push_module

Re: Nginx HTTP Push Module

#4

Post by danfitch » Thu, Nov 19, 2009, 3:29 PM UTC

Site isn't working for me, but the github url is http://github.com/slact/nginx_http_push_module

Re: Nginx HTTP Push Module

#5

Post by steve19 » Thu, Nov 19, 2009, 3:48 PM UTC

This blog post explains it better : http://www.igvita.com/2009/10/21/nginx-comet-low-latency-ser...

Re: Nginx HTTP Push Module

#6

Post by slact » Thu, Nov 19, 2009, 4:53 PM UTC

Beep. I wrote this. Questions, comments -- ask away.

Re: Nginx HTTP Push Module

#7

Post by slact » Thu, Nov 19, 2009, 4:59 PM UTC

thijsterlouw wrote: post #2

did anyone already do performance tests? I'm especially interested in memory and cpu usage. Any limitations?

Everything is pretty much as efficient as vanilla nginx. There are some O(log(n)) lookups, but i've not noticed CPU usage hit anything even remotely suspicious (fixed bugs aside).

Memory usage for long-polling requests is regular nginx usage ("2.5MB for 10K idle connections"), + around a hundred bytes or so per ling-polling requests. A channel eats up about a dozen bytes.

The only limitation that one might run into is the maximum memory allotted for shared messages -- but that's a configurable value.

Re: Nginx HTTP Push Module

#8

Post by diegomsana » Thu, Nov 19, 2009, 6:44 PM UTC

slact wrote: post #6

Beep. I wrote this. Questions, comments -- ask away.

I haven't tried to implement this yet, so i have no question so far. But i'd like to compliment you for this incredible useful module. Keep it up :)

Re: Nginx HTTP Push Module

#9

Post by karanbhangui » Fri, Nov 20, 2009, 2:29 PM UTC

slact wrote: post #6

Beep. I wrote this. Questions, comments -- ask away.

Could you explain to the layman how this compares to the web server that ships with Tornado? I mean more in terms of usecases rather than performance. Also, the entire Tornado stack is written to be async and non-blocking. If one was to use something like plain vanilla PHP behind your nginx module, would one get the same result? Cheers.

Re: Nginx HTTP Push Module

#10

Post by bham » Sat, Nov 21, 2009, 4:42 AM UTC

slact wrote: post #6

Beep. I wrote this. Questions, comments -- ask away.

This looks fantastic. Thanks for writing it.

How would you go about restricting access to channels to a specific user or users? My first take would be to issue an unguessable id upon successful authentication and use this id as the channel id -- a shared secret. Only those who should know the id do know it.

I don't see support for streaming; the connection to the long-polling client is closed after consuming. Are you planning on adding support for streaming new messages as they are published?