Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buffer output of running step, transmit pages #37

Open
sroidl opened this issue Nov 15, 2016 · 2 comments
Open

Buffer output of running step, transmit pages #37

sroidl opened this issue Nov 15, 2016 · 2 comments

Comments

@sroidl
Copy link
Owner

sroidl commented Nov 15, 2016

at the moment, every single update of a running step (i.e. every line out output) triggers an update to the UI. The result is that the transmission of large chunks of output (e.g. result of a large output step) takes a long time (i.e. longer than the step itself).

this could be solved by dropping updates and not sending intermediate updates if a newer one is available

@sroidl sroidl assigned mgeissen and sroidl and unassigned mgeissen Nov 15, 2016
@sroidl sroidl added qa and removed ready labels Nov 28, 2016
@sroidl
Copy link
Owner Author

sroidl commented Nov 28, 2016

output is updated only once per second, thus limiting the amount of network traffic sent to the client.
this solution should be evaluated

@sroidl sroidl removed their assignment Dec 12, 2016
@sroidl
Copy link
Owner Author

sroidl commented Dec 12, 2016

todo: use async.core mechanisms (throttling channel) instead of half baked own solution

@sroidl sroidl added ready and removed qa labels Dec 12, 2016
@sroidl sroidl removed the ready label Jan 11, 2017
@sroidl sroidl added the ready label Jan 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants