Return-Path: 
 <user-return-29472-apmail-commons-user-archive=commons.apache.org@commons.apache.org>
X-Original-To: apmail-commons-user-archive@www.apache.org
Delivered-To: apmail-commons-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 2312C17CCC
	for <apmail-commons-user-archive@www.apache.org>;
 Thu,  9 Oct 2014 14:02:50 +0000 (UTC)
Received: (qmail 50195 invoked by uid 500); 9 Oct 2014 14:02:48 -0000
Delivered-To: apmail-commons-user-archive@commons.apache.org
Received: (qmail 50089 invoked by uid 500); 9 Oct 2014 14:02:48 -0000
Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@commons.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@commons.apache.org>
List-Post: <mailto:user@commons.apache.org>
List-Id: <user.commons.apache.org>
Reply-To: "Commons Users List" <user@commons.apache.org>
Delivered-To: mailing list user@commons.apache.org
Received: (qmail 50048 invoked by uid 99); 9 Oct 2014 14:02:48 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2014 14:02:48 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of arnout.cator@gmail.com
 designates 209.85.218.41 as permitted sender)
Received: from [209.85.218.41] (HELO mail-oi0-f41.google.com) (209.85.218.41)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2014 14:02:43 +0000
Received: by mail-oi0-f41.google.com with SMTP id u20so2782120oif.28
        for <user@commons.apache.org>; Thu, 09 Oct 2014 07:02:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=zpa+YcYg/YvkUAjELudJwj2vRuEj3vrTEGbA5M+3QhE=;
        b=Yh9ghrtsclSUP5wuJwbLqWanSem1OCoTW9ocTzxAIY/f2H3rJbdHrOz8ULNCI+pMlk
         Y+JO2fyRwaqvo2Igxh9rKhEr8ospJQ6iGX8vMiY3D2frESCyohGQokH7hxsceNtor0MD
         eSR3tsbNHrO+TW5gZ8/TZvtRuOuOPVv3wMeB/Vr33RfEYhYuTH+hb61FzQiVGNgiT/L1
         +TQ+TbzBf2RxqfyoEuda7tzMHTG2DjJRjVE7EuVxZF0ghiQzD/1azLUKA6WI7S1HIbrA
         uZucEjxFmsHMsGC1Ao0pBMESnbog64Ea2PuS9uiZjQMpo1+0InaVn7B7n7GmGAZXcUoy
         KJDQ==
MIME-Version: 1.0
X-Received: by 10.182.33.99 with SMTP id q3mr23467962obi.28.1412863342452;
 Thu, 09 Oct 2014 07:02:22 -0700 (PDT)
Received: by 10.76.105.4 with HTTP; Thu, 9 Oct 2014 07:02:22 -0700 (PDT)
Date: Thu, 9 Oct 2014 15:02:22 +0100
Message-ID: 
 <CAJRUzk4n+yvuSzNSyuQiKTm7bVBDCHa3nF9=rTLuNSpxs3u6KQ@mail.gmail.com>
Subject: JCS cache benchmarking for performance
From: arnout cator <arnout.cator@gmail.com>
To: user@commons.apache.org
Content-Type: multipart/alternative; boundary=001a11c1f286a4a8d40504fde1cb
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c1f286a4a8d40504fde1cb
Content-Type: text/plain; charset=UTF-8

Hi,

I have the following question:

What would be the best practice in monitoring JCS caching performance for
production web applications? I am looking for a way to collect data and
then give advice on sizing of web applications that heavily use JCS for
caching of java objects.

--001a11c1f286a4a8d40504fde1cb--