<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: memcached_debug.c ?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>We'd definitely welcome such a module, we've only just started working with memcached but we would like to do some profiling of our app. This would help a lot.<BR>
<BR>
<BR>
Regards,<BR>
Kieran Benton<BR>
Senior Developer<BR>
<BR>
Ticketmaster Systems Ltd. (Formerly Synchro Systems Ltd.) <BR>
48 Leceister Square, London, WC2H 7LR<BR>
<BR>
T: +44 (0) 207 344 4000<BR>
F: +44 (0) 207 915 0418<BR>
E: kieran.benton@ticketmaster.co.uk<BR>
<BR>
-----------------------------------<BR>
This message was sent by Blackberry<BR>
<BR>
-----Original Message-----<BR>
From: memcached-bounces@lists.danga.com <memcached-bounces@lists.danga.com><BR>
To: Memcached list <memcached@lists.danga.com><BR>
Sent: Wed Jun 13 19:09:27 2007<BR>
Subject: memcached_debug.c ?<BR>
<BR>
<BR>
How would people feel about adding a "memcached_debug.c" file to the <BR>
repository, that contains extensions that are not approved/<BR>
sanctioned? For example, this would be the perfect place to put a <BR>
"keys" command, in order to find out what keys are currently in the <BR>
instance, or perhaps a "free_mem" command that evicted everything <BR>
expired and returned the amount of free memory?<BR>
<BR>
The idea is that these commands would only be available in the debug <BR>
version of memcache; this would be the version to deploy to QA & <BR>
staging environments, where performance is less important than the <BR>
ability to look under the hood, so to speak.<BR>
<BR>
Thoughts?<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>