>>> On 9/7/2007 at 6:26 PM, in message <[EMAIL PROTECTED]>, "Chris Slaughter" <[EMAIL PROTECTED]> wrote: > The problem is that memory is currently stored as an uint32, so it overflows > at a little over 4TB. Since it is hardcoded, 32- vs. 64-bit doesn't make a > difference. > > I took a look at the code at one point, but it wasn't as simple as changing > it to a uint64, so I took the route of 'fudging' all of the memory values. > I ended up dividing the values by 1024, and then adding a hack in the graph > so the values are displayed as T instead of M... >
Of course this issue could be easily taken care of in 3.1.x by writing a simple plugable python module that handles memory as uint64. "Shameless plug for Ganglia 3.1.x" ;) Brad ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
