Want to take your software engineering career to the next level? Join the mailing list for career tips & advice Click here

memkeys

a top like tool for inspecting memcache key values in realtime

Subscribe to updates I use memkeys


Statistics on memkeys

Number of watchers on Github 354
Number of open issues 0
Main language C++
Average time to merge a PR 5 days
Open pull requests 0+
Closed pull requests 1+
Last commit over 7 years ago
Repo Created over 7 years ago
Repo Last Updated over 2 years ago
Size 410 KB
Organization / Authortumblr
Contributors1
Page Updated
Do you use memkeys? Leave a review!
View memkeys activity
View on github
Book a Mock Interview With Me (Silicon Valley Engineering Leader, 100s of interviews conducted)
Software engineers: It's time to get promoted. Starting NOW! Subscribe to my mailing list and I will equip you with tools, tips and actionable advice to grow in your career.
Evaluating memkeys for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)

memkeys

Show your memcache key usage in realtime.

This was originally inspired by mctop from etsy. I found that under load mctop would drop between 50 and 75 percent of packets. Under the same load memkeys will typically drop less than 3 percent of packets. This is on a machine saturating a 1Gb network link.

Command line options

Usage: memkeys -i NIC [options]
    -d, --discard=THRESH        Discard keys where req/s rate is below THRESH
    -i, --interface=NIC         Network interface to capture traffic on (required)
    -p, --port=PORT             Network port to capture memcache traffic on (default 11211)
    -r, --refresh=INTERVAL      Refresh the stats display every INTERVAL ms (default 500)
    -l, --logfile=FILE          Output logs to FILE
    -R, --report=REPORT         Output data in REPORT format (CSV or curses, default curses)

    -h, --help                  This help
    -v, --verbose               Increase verbosity. May be used multiple times.
    -V, --version               Show program info and exit.

Running

You will most likely want to run with something like:

memkeys -i eth0 -l /tmp/memkeys.log

If you are running memkeys on a very high traffic machine you will want to specify a discard threshold, otherwise the memory footprint will grow quite large.

memkeys -i eth0 -d 10.0 -l /tmp/memkeys.log

Screenshot

Screenshot

Development/Build

Install gperftools and gperftools-devel if you want to build with --enable-profiling. You will typically want to configure with --enable-debug, and possibly with --enable-development. The latter two options will enable additional error logging.

You will need libpcap-devel, libpcrecpp, and libncurses-devel.

memkeys was developed on CentOS 5.8 with the following software tools:

GCC version    : g++44 (GCC) 4.4.6 20110731 (Red Hat 4.4.6-3)
GNU gmake      : 3.81
ld             : 2.17.50.0.6-20
coreutils      : 5.97
libtool        : 2.4.2
autoconf       : 2.68
automake       : 1.9.6

The following library versions were used:

libpcap-devel  : 0.9.4-15
pcre-devel     : 6.6-6
ncurses-devel  : 5.5-24.20060715

This should build fine against newer versions of the above tools. Different libraries are untested.

License

Copyright 2013 Tumblr.

Licensed under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

memkeys questions on Stackoverflow (View All Questions)
  • Cannot configure/build memkeys (a memcached activity app)
memkeys list of languages used
Other projects in C++
Powered by Autocode - Instant Webhooks, Scripts and APIs
Autocode logo wordmark