Skip to content
This repository has been archived by the owner on Jan 8, 2019. It is now read-only.

Bundle stream throughput ajax requests #779

Closed
Mowee opened this issue May 14, 2014 · 4 comments
Closed

Bundle stream throughput ajax requests #779

Mowee opened this issue May 14, 2014 · 4 comments
Assignees
Labels
Milestone

Comments

@Mowee
Copy link

Mowee commented May 14, 2014

At this moment I have about 50 Streams pre configured for everybody. Every stream fires his own json request to get the current throughput. I find this highly ineffectiv because with so many streams the page slows down.

Suggestion: One json request to get all the throughput information that are needed.

@dennisoelkers
Copy link
Contributor

Agreed. You have a point there, not much more to say.

@dennisoelkers dennisoelkers added this to the gemini milestone May 14, 2014
@dennisoelkers dennisoelkers self-assigned this May 14, 2014
@kroepke
Copy link
Contributor

kroepke commented May 26, 2014

Also +1
This applies to many periodical tasks, although streams are most likely the heaviest.
Should be easy to implement a bulk endpoint for them.

@kroepke kroepke modified the milestones: 0.21, gemini Jun 4, 2014
@kroepke kroepke changed the title Multiple Streams Bundle stream throughput ajax requests Jul 3, 2014
@dennisoelkers dennisoelkers modified the milestones: 0.90.1, 0.92 Oct 13, 2014
@joschi joschi modified the milestone: 0.92 Jan 13, 2015
@kroepke kroepke assigned kroepke and unassigned dennisoelkers Apr 15, 2015
@kroepke kroepke added this to the 1.1.0 milestone Apr 15, 2015
@kroepke
Copy link
Contributor

kroepke commented Apr 15, 2015

This has been addressed by various commits. We are now using a single websocket connection (or fall back to ajax polling) to gather metrics for various updating numbers around the ui.

The only remaining ajax call should be getting the notifications for the menubar, but that's nothing is done per-stream or so.

@kroepke kroepke closed this as completed Apr 15, 2015
@kroepke
Copy link
Contributor

kroepke commented Apr 15, 2015

Specifically 380182c

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants