scaling: add used memory to PDF report table #279
Conversation
|
Looking good @askervin . Code looks good, and it ran and made a table for me... a couple of questions:
I also suspect once we have settled on which result is 'best' (most representative of theoretical maximum pod density), we should also note that in the |
|
Good points, thanks @grahamwhaley. I added the memory used plot. Now the page looks more complete, and the title offered a nice place to explain what "used" actually means. (That is, why $\delta$Free > $\delta$Used.) A note on grabbing used memory stats added to Rmd as well. |
There was a problem hiding this comment.
lgtm
I see the graphs and data. Tested with 1x1k and 2x2k datasets.
I'm hoping once we merge/meld along with #280 then it will look even nice :-)
Currently the PDF report shows how much scaling up consumes free memory. This number is not comparable between cluster nodes or even test runs because RAM used for OS caches/buffers/slab is counted as consumed. As a consequence, consumed free memory depends heavily on initial memory conditions of a node, instead of used memory by the k8s and pods. This patch adds "memory used" to the report in order to have less node-dependent and more reproducible memory figure. Using /proc/meminfo "MemAvailable" was also tried out, but it varies almost like "MemFree" that is currently reported. Signed-off-by: Antti Kervinen <[email protected]>
askervin
force-pushed
the
53m_mem_used
branch
from
71e4f9c to
dc9f9a7
Compare
|
rebased, commits squashed, tested, ready for merge. |
Currently the PDF report shows how much scaling up consumes free
memory. This number is not comparable between cluster nodes or even
test runs because RAM used for OS caches/buffers/slab is counted as
consumed. As a consequence, consumed free memory depends heavily on
initial memory conditions of a node, instead of used memory by the k8s
and pods. This patch adds "memory used" to the report in order to have
less node-dependent and more reproducible memory figure.
Using /proc/meminfo "MemAvailable" was also tried out, but it varies
almost like "MemFree" that is currently reported.
Signed-off-by: Antti Kervinen [email protected]