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

machines: amount of RAM and how it's used is separate #8052

Closed
andreasn opened this issue Nov 9, 2017 · 5 comments
Closed

machines: amount of RAM and how it's used is separate #8052

andreasn opened this issue Nov 9, 2017 · 5 comments

Comments

@andreasn
Copy link
Contributor

andreasn commented Nov 9, 2017

So I can see that I have 1000 MiB RAM on my VM, but the only way to see how it's utilized is if I jump over to the performance tab.
So I wonder if it makes sense to put the stats directly in the Overview tab.

@andreasn
Copy link
Contributor Author

andreasn commented Nov 9, 2017

Usage is pretty empty by itself anyway.

@mareklibra
Copy link
Contributor

@andreasn , good idea.
Formerly, the Usage subtab was meant not only for memory/cpu but for networks and disks as well.
But this is recently not yet implemented.
Such a statistic might fit the "Overview" subtab well.

I can imagine some small graphics representation of how much memory/cpu is consumed/available on the Overview subtab. We would get rid of the donut charts completely.

Anyway, this might be tricky from performance perspective.
Collecting of such "usage" data is quite expensive operation since polling is required.

Recently, the polling is started/ended when corresponding subtab is opened/left.
We can do the same thing on the Overview subtab, but load will be increased.

We might make use of 3rd party collecting tool (like PCP) but this would bring another dependency to get cockpit-machines working.

@martinpitt , what do you think?

@martinpitt
Copy link
Member

@andreasn: What do you mean by "performance tab"? "Usage" maybe? We already start polling per machine once you activate the "Usage" tab, and as this is (deliberately) not the default tab we can limit the performance hit and avoid immediately polling all VMs (which can be numerous!). Once we do poll, then I figure showing more details from the poll should be fine.

If the target machine has PCP installed and enabled we could use it of course, but (1) we can't generally peek into the VM too much as a we don't know how to log in, and (2) PCP isn't commonly found in VMs so we need a good fallback.

@KKoukiou
Copy link
Contributor

TBH I like the separation of VM configuration details in the overview tab, which we just fetch from the libvirt xml and utilization data in other tab. @andreasn unless you have strong opinion here would you mind if I closed this?

@KKoukiou
Copy link
Contributor

@andreasn I am closing this since it's horribly outdated - if you think it still makes still sense I will be glad to refactor the whole VM row according to some mockup.

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

No branches or pull requests

4 participants