Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

Default workflows, problem with CPU/memory usage #809

Open
dragoslav opened this issue Oct 28, 2016 · 3 comments
Open

Default workflows, problem with CPU/memory usage #809

dragoslav opened this issue Oct 28, 2016 · 3 comments
Labels
Milestone

Comments

@dragoslav
Copy link
Contributor

"... it is running ok for like 2-3 hours then gradually getting a lot of cpu time, then they (the machine) starts swapping. ... If I restart both dockers in marathon it looks ok for a couple of hours before the issue begins happening again."

@dragoslav dragoslav added this to the 0.9.x milestone Oct 28, 2016
@dragoslav dragoslav added the bug label Oct 28, 2016
@dragoslav
Copy link
Contributor Author

This issue should be resolved by #813, but still requires further testing/confirmation.

@olafmol
Copy link
Member

olafmol commented Feb 14, 2017

first we need to add metric collection to workflows, then we should create a stress-test environment and scripts @iamtew

@iamtew
Copy link
Contributor

iamtew commented Feb 17, 2017

metricbeat is available in the workflow agent, see: magneticio/vamp-workflow-agent#10

gateway agent is almost there: https://github.com/magneticio/vamp-gateway-agent/tree/metricbeat

vamp container itself is planned, but not yet implemented: magneticio/vamp-docker-images#21

@iamtew iamtew removed their assignment Mar 29, 2017
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

3 participants