Do something with every second polling

[Kagami]

At first I would like to thank you for the great software. I'm really enjoy using it.

But some thing really scary me:
For some reason I opened the web-console while using the Graylog web interface and it's really surprised me what I saw there: https://f.cloud.github.com/assets/533383/2279772/9a6523b2-9f78-11e3-89a1-4896b07d7e8f.png

It naturally sends AJAX request every second. Why don't you use WebSockets (available in every modern browser, even IE) or long polling at worst?

The same behaviour appears if I log in (it starts polling /a/system/throughput instead). And on the streams page even worse: AJAX request for every stream every second. What if I have hundred streams? And the same for the widgets. I already have 8 widgets so it's 9 seconds per second for just single web page.

I would love to see this fixed. Thanks.

I'm using the latest graylog2-server (0.20.1) and latest graylog2-web (0.20.1). Tested with Google Chrome 33.0.1750.117.

[lennartkoopmann]

We are not planning to migrate away from the AJAX requests for now (and WebSockets are not supported in IE9 which we need to support) but there certainly is space to improve and group some together into single calls. Keeping this ticket open for that.

[Kagami]

For IE9 Flash or long polling fallback could be used. There are plenty of libraries which provide this transparently: web-socket-js, socket.io for example.

[lennartkoopmann]

That's true - You are right that this would be technically possible.

It would however require changing everything there from polling to a pubsub approach - And we don't see the technical necessity to invest too much time into that right now. It might be nicer to have, but so far we did not see any performance problems with a polling approach - Even in setups with billions of messages.

[Kagami]

I do not care about perfomance issues on the server-side since I'm using personal setup of the graylog and only a few people have access to it.
But I do care about client-side: though for now with 8 widgets I can't recognize noticeable browser slowness but I will definetely do with 50-100 widgets. And think about the mobiles and people with slow Internet connections: they just cannot use interface which makes tons of requests per second.
So at least compromise solution by using single AJAX-request for updating all widgets at once would be nice thing to have.

Btw, why are AJAX requests sent every second when I have widgets cached for 10 seconds (default)? Is it a bug or feature?

[lennartkoopmann]

Yes, we already started consolidating the node throughput calls per input into one AJAX call and not multiple calls for every single input.

[dennisoelkers]

Duplicate of #779

[kroepke]

This issue has been partly addressed by #1214 #1182 and #779 (see comment there)

The widgets are still polling but we will address that in a future version.

[bernd]

Closing this because we are working on fixing this.