[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] strange graph behavior - random machines & graphs
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] strange graph behavior - random machines & graphs
- From: "Gary Baluha" <gumby3203 (at) gmail.com>
- Date: Wed, 19 Dec 2007 09:59:39 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=x3JDH1l3mcjzk+5UojLZFS16gC2/9WfPjf4MYKQ7toY=; b=JU9a5xdkF8X2E15sha5IkPi37epeON94VPrNynqd/b5gN099VkPnA5IesDPJKb6gZ9Wt9dq5hjDtor+xNm8FBYgTPqPf98L+KlhC+e7y7sa5ABmTiXMsWXWT62URV0BNsim35fcnik040E13RE9GBPfE5o7PH/uVtZqN+Zh1gas=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=p5CAIm4nrs7DM0yr0fH+DXAb9HfkHkihc3Hv25tniFJjCVRy3/cILDF3u81tehwH94LkeHqgmfCgMfkph6a2Hlv2mZkZXHDhTMD/EEi3BqplzsYplDrdIcqF/k1miFtpyTcc2l4COODc3g0SZI+uObTCq6LumW1Uw54HhR5zPgM=
- References: <29f517690712050853u4d47ef3cr25fc15f538cdf85c (at) mail.gmail.com> <961092e10712060802g2e18c65fj4810231c3384caa4 (at) mail.gmail.com> <29f517690712071213k1c0214a2of2eb6ff400815004 (at) mail.gmail.com> <58EF0861D3A1A04182720B3A5231C7C201EA5138 (at) usplm205.amer.corp.eds.com> <29f517690712110642r7aa2c073wb23409bc1bb71bad (at) mail.gmail.com> <29f517690712120714y2a40280cib186239487583d32 (at) mail.gmail.com> <6C2B32F89382AF42875672B6F5BEB68204F54885 (at) MERCMBX07.na.sas.com> <961092e10712120728o906c216hec40c55ae9f0ece4 (at) mail.gmail.com> <6C2B32F89382AF42875672B6F5BEB68204F548B6 (at) MERCMBX07.na.sas.com> <29f517690712121045l3da75cc3ib5daf8ef86a7ab6c (at) mail.gmail.com>
It's interesting that it seems the CPU Load and Users and Processes graphs
are the graphs that are most likely to have this strange corruption. I have
also seen it on a few Disk graphs, but not nearly as many as the other two
graphs. Interestingly, the CPU Utilization, Network I/O, and TCP Connection
Times graphs have _never_ had this corruption. I'd also like to say the
Memory Utilization graph hasn't had this issue either, though I can't recall
with complete certainty that that is the case.
I wonder what the main difference between the 3 graphs that do have the
issue is, and the 3 (possibly 4) graphs that have never exhibited this
issue. There must be some physical difference, as I can't imagine it is all
do purely to luck...