Well I took a look at the scripting option and assuming you meant escript, 
it doesn't look like something I'll be picking up from scratch in an hour 
or so ;)

I hacked port_sigar as you suggested to print the reply values to stderr 
and ran it using the example.escript which is in the source directory ( I 
hope that was a reasonable thing to do).

Here is the output from one of the couchbase servers:

./portsigar/example.escript
cpu_total_ms: 67285756633
cpu_idle_ms: 32306446002
swap_total: 8589934592
swap_used: 1717555200
swap_page_in: 5915867
swap_page_out: 87010188
mem_total: 4294967296
mem_used: 18446744073677623296
mem_actual_used: 18446744017909834968
mem_actual_free: 60094683944
escript: exception error: no match of right hand side value
                
 <<2,0,0,0,40,3,0,0,217,42,139,170,15,0,0,0,178,62,157,133,7,0,
                  
 0,0,0,0,0,0,2,0,0,0,0,208,95,102,0,0,0,0,219,68,90,0,0,0,0,
                   0,140,...>>

Obviously the mem_used and mem_actual_used numbers are way off.
I dug into it deeper and it seems the calculations made by sigar are wrong 
when running inside a zone.
I'll keep looking for a long term solution to that but the thing is that 
these calculations in sigar haven't changed in 3 years so what changed in 
2.5.1 that caused the numbers in the interface to come out screwy?

Thanks,
Yonah




On Wednesday, July 2, 2014 10:46:51 PM UTC+3, Aliaksey Kandratsenka wrote:
>
>
>
>
> On Wed, Jul 2, 2014 at 7:56 AM, Yonah Russ <[email protected] 
> <javascript:>> wrote:
>
>> Hi,
>>
>> I've rebuilt after reverting this commit and the problem persists.
>> I do see that there are many other occurrences of  MemActualFree. 
>> Maybe there are a couple other places that need to be fixed?
>>
>> Is there any other info I can provide?
>>
>
> One option is to try to hack sigar_port.c. And fork a version that prints 
> out stuff in human readable way rather than outputting raw structs. Or if 
> you're comfortable with scripting you can write a simple script that will 
> spawn sigar_port and read it's output, then decode and print it. This way 
> we can see what values we're getting out of it for memory usage stats.
>
> If you choose second option, feel free to submit it. It might be 
> occasionally useful script to have.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Couchbase" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to