Looks like a bug in the sample workbook. Thanks for reporting this. We will get a corrected version of the sample workbook up on Git ASAP and will post here when that happens.
Over 90% graph of our %committed bytes is over 100% as shown in below snapshot. Thanks for this post. And based on the reply by Justin I believe this is wrong metrics. Just checking if there was any update on this, and I missed it.
And if no updates, then have you made any changes to keep 100% as upper limit ?.
Not that I'm aware of. I haven't made any changes.
I was thinking since we are having multiple core machine such as 8 cores, shouldn't that be the reason behind reaching more than 100% as upper limit ? In same way as looking into %CPU readings on tableau processes are reaching more that 100%
Given Justin's reply I doubt it but I haven't had the time to really investigate it.
I haven't seen this on Memory, but I did see this on CPU. I have an open post on this here Tabmon CPU % anomolies.
The root cause seems to be that the Windows Perfmon counters (the row-level data behind TabMon) are actually reporting greater than 100% for a single row of performance recording data. See the attached screenshot in the other post.
I spoke with Tableau support about this a few weeks ago, but I still don't have an answer.
President & Chief Architect
3 of 3 people found this helpful
There was an unfortunate error in an early version of the sample workbook that would explain this. If you check the underlying sheet, the aggregation on this counter should be AVG (and not SUM). If that turns out to be the issue, I apologize for the confusion.
To the best of my knowledge, it should not be possible for % Committed Bytes In Use to ever exceed 100%.
Thanks for getting back on this. I really appreciate the reply's and feedback am getting here.
Will be waiting for the Tabmon part 2 then .