ccortezb/memcache-top

Automatically exported from code.google.com/p/memcache-top

memcache-top's Issues

No help output

Read the summary line.

Original issue reported on code.google.com by [email protected] on 7 Nov 2010 at 1:38

Output doesn't look good when using hostnames

What steps will reproduce the problem?
1. Use a hostname (for example memcache1.myawesomeapplication.com) in the
config
2. Notice that all the columns are shifted

Also, the output doesn't seem to stay at the top of my screen, like for
example mytop or top does, so the refresh looks a bit sluggish and a bit ugly..

Original issue reported on code.google.com by [email protected] on 22 Apr 2009 at 7:42

Add one-off display mode

"memcache-top is a very nifty app, which has helped expose issues we had with 
excess evictions from our memcached (excess=more than zero!). the only 
'shortcoming' i can find is the lack of a "one-shot" run option - i'd really 
like to incorporate the output into a daily report, but redirecting the 
output to a file is a bit of a fail...."

Original issue reported on code.google.com by [email protected] on 16 Jul 2009 at 9:03

Can't locate Time/HiRes.pm

What steps will reproduce the problem?
1. perl  memcache-top-v0.6

What is the expected output? What do you see instead?

I see this error

Can't locate Time/HiRes.pm in @INC (@INC contains: /usr/local/lib64/perl5 
/usr/local/share/perl5 /usr/lib64/perl5/vendor_perl 
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at 
memcache-top-v0.6 line 59.
BEGIN failed--compilation aborted at memcache-top-v0.6 line 59.


What version of the product are you using? On what operating system?

Centos 6.3 64 bits

Please provide any additional information below.

I solved using

yum install perl-Time-HiRes

Original issue reported on code.google.com by a.sanchez75 on 17 Nov 2012 at 4:53

New Feature: run once option

Adds an option '--once' to cause memcache-top to run once then exit. Makes
it useful in cronjobs and scripts.

Diff:

diff memcache-top.pl memcache-top.pl.orig 
20d19
< #     - Run once and exit --once (good for scripting)
64c63
<     $commands, $cumulative, $once);

---
>     $commands, $cumulative);
139d137
<       'once'          => \$once,
382c380
<   push @out,"\n(ctrl-c to quit.)\n" if !$once;

---
>   push @out,"\n(ctrl-c to quit.)\n";
384c382
<   push @out, "\n" if $once;

---
> 
386,387d383
<   
<   exit(0) if $once;

Original issue reported on code.google.com by jason%[email protected] on 18 Nov 2009 at 9:33

• Merged into: #2

Attachments:

• memcache-top.pl

Use of 'instances' is confusing, use 'hosts'

Most scripts use the term host vs. instance. -h and --hosts flags would be
great.

Original issue reported on code.google.com by [email protected] on 29 Oct 2009 at 12:05

Enhancement Patch

Hi,
i made some simple enhancements for memcache-top (see attached patch, see 
attached script).


- Added a option "-h" to show documentation with perldoc and basic 
documentation at the end of the script.
- Added the ability to use this tool for logging to a pipe ("-l").
- Added the ability to monitor the uptime.

Probably you can add this to memcache-top?
If you have some improvement idease, please let me know....

Probably i will also submit patches in future.... :-)

Regards
Marc

Original issue reported on code.google.com by [email protected] on 25 Jun 2012 at 10:11

Attachments:

• memcache-top
• patch_based_on_r6.diff

display curr_items

Would like to be able to see cur_items as well.

I've included a patch.

Original issue reported on code.google.com by [email protected] on 17 Dec 2010 at 4:48

Attachments:

• curr_items.patch

Illegal division by zero using cumulativeand a flushed memcached instance

What steps will reproduce the problem?
1. Start memcache and start memcached-top with --cumulative
2. Flush memcached
3. You get the error

What is the expected output? What do you see instead?

Not to fail.

Received this: Illegal division by zero at ./memcache-top line 285.

What version of the product are you using? On what operating system?

v0.6

Please provide any additional information below.

This happens with single or multiple instances monitoring.

Original issue reported on code.google.com by luislavena on 8 Jul 2010 at 11:37

Add support for unix sockets

memcache can also work with unix sockets instead of tcp/ip. This should even be 
faster.

This patch adds support to connect to unix sockets, simple give the path to a 
unix sockets en memcache-top will connect to it.

Original issue reported on code.google.com by [email protected] on 12 Aug 2013 at 11:44

Attachments:

• 0001-Added-support-for-unix-sockets.patch

Feature Request: Config file?

It would be useful to have ~/.memcache-top.conf which could take newline 
separated instances to make running the command easier?

Original issue reported on code.google.com by [email protected] on 28 Nov 2012 at 4:51

Incorrect calculation of cache_hit parameter

What steps will reproduce the problem?
1. Run the memcache-top with --nolifetime option and short sleep time (say 5 
seconds)
2. Look at the evolution of the calculated cache_hit
3. Compare the observed values of the cache_hit parameter with similar values 
calculated in another way (say manually or automatically)

What is the expected output? What do you see instead?
We obtain that many cache_hit values are often zero but this do not match the 
real memcached state.

What version of the product are you using? On what operating system?
0.6 on many Linux RedHat 5.x and Mac OS X

Please provide any additional information below.
Analizing the problem I have found that the initialization value (equal to 
zero) of cache_hit variable is used also when we do not have cache misses. 
Infact, look at the following code lines (lines 292-295 of version 0.6 of the 
script):

  $outstats{cache_hit} = 0;
  if ( defined($outstats{get_misses}) && $outstats{get_misses} > 0 ) {
          $outstats{cache_hit} = ( $laststats{$instance}{get_hits} / $laststats{$instance}{cmd_get} ) * 100;
  }

In the case of nolifetime the get_misses is calculated as variation from the 
previous value. The script calculate the cache_hit only if get_misses is bigger 
than zero. I think that this is not correct, because we can have no variation 
of the get_misses value (no misses) and at the same time have a variation of 
the get_hits and cmd_get values (cache hits). I propose then the following 
modification:

  $outstats{cache_hit} = 0;
  if ( defined($outstats{get_misses}) && $outstats{get_misses} >= 0 ) {
          $outstats{cache_hit} = ( $laststats{$instance}{get_hits} / $laststats{$instance}{cmd_get} ) * 100;
  }

into which the cache_hit is calculated also when we do not have cache misses.

Attached you can find our current version of the script that has also some 
minor changes, like the possibility to log the measured data to file for 
post-process purposes and a simple command line help.

Massimiliano

Original issue reported on code.google.com by [email protected] on 30 Aug 2012 at 8:59

Not all instance showing memcache-top

What steps will reproduce the problem?
1. memcache-top
2.
3.

What is the expected output? What do you see instead?
I expect 'memcache-top' to show me all instances
'memcache-top' shows me 1 instance: 127.0.0.1:11211 is DOWN
'memcache-top --instances 127.0.0.1:18941' gives me actual/live result of 18941


What version of the product are you using? On what operating system?
v0.6 linux fedora 15


Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 29 Jun 2012 at 9:14

Illegal division by zero at ./memcachetop-broken line 294

Quick and dirty fix:


>   if ( $laststats{$instance}{cmd_get} > 0) {
294a296
>   }

Original issue reported on code.google.com by [email protected] on 15 Jul 2010 at 4:57