Return-Path: X-Original-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9A753D425 for ; Wed, 26 Sep 2012 21:38:58 +0000 (UTC) Received: (qmail 97694 invoked by uid 500); 26 Sep 2012 21:38:58 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 97650 invoked by uid 500); 26 Sep 2012 21:38:58 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 97642 invoked by uid 99); 26 Sep 2012 21:38:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 21:38:58 +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 jmarantz@google.com designates 209.85.214.45 as permitted sender) Received: from [209.85.214.45] (HELO mail-bk0-f45.google.com) (209.85.214.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 21:38:51 +0000 Received: by bkcjf3 with SMTP id jf3so152484bkc.18 for ; Wed, 26 Sep 2012 14:38:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-system-of-record; bh=/TVn50PYoOiu1s3w8a8U+1qwNlV2ApI7OFhON71C9D4=; b=DkI5j/NQVnWl7TVK8gIRtld7AawKu5I9TZOrfLJcFQXl0WXAEDo19ChII+BbnE4iMc Wwh+4lzbEw+4OH3jYVgYRa6g9eDDxmY/5bNOE8cOUaHvTxh+NZ7btD99OJle7UfrY24e cOpC5EbhW04h3prShn150U1yZL3GD26vm8J11izpxUjKq6sbahdpV26HWeq/nAVs65XU F2zPYG/28v5f1at1aQwuXM3Bqz7FPMSrQ5c6uoTf1Dx5urOc5WxFZ+boMaPGeMZqnH5E cpqE87SK8IJ3Xoa0ar73p5YkwCzdUjCz6KE5qoOCTCDa/ONmmU53UV7rVn2Md+hqXPNj /m0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-system-of-record:x-gm-message-state; bh=/TVn50PYoOiu1s3w8a8U+1qwNlV2ApI7OFhON71C9D4=; b=ibpjE1zViA9Bx8519G202uDpTgepYERLY1Tw43rP9GNegJQLhbXOvrO5POZCvVpjiI mpbWl4XmVX9rLM3ftqZOme3VPCR77aMrKBAD7aw/h3j2cxeME5M4gq2a5nueV3pxdT0d KCWjJ3eqiU8vYOuO36YoBmroHH2kjtd4R02jCJ8ahxthB0KwswkvhiuKnzZ2H+c3sqAV iA124uIDnJu7xYllQJm4QjIvOMzVVvHrsjw+Q7iUORysumqqwELAOglw21vEbUbmUPcC PHD/3xCMgajVCP0wtucAqIVHsASHxxmPRIS/WSaMgZY4n3EVv8V6/oOaG/t6XST0MsFO MoUw== Received: by 10.152.122.9 with SMTP id lo9mr1633514lab.41.1348695510091; Wed, 26 Sep 2012 14:38:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.80.233 with HTTP; Wed, 26 Sep 2012 14:38:09 -0700 (PDT) From: Joshua Marantz Date: Wed, 26 Sep 2012 17:38:09 -0400 Message-ID: Subject: aprmemcache question To: "modules-dev@httpd.apache.org" Content-Type: multipart/alternative; boundary=f46d043bd6faca06e504caa1a424 X-System-Of-Record: true X-Gm-Message-State: ALoCoQnmFyFmRPjYcmavLZfplbnpHpTmml91WjR0+1hGl/xnSoNnoYRUs4I5Cbh2FMWZ08kCmvuYjFg5Y6GqPc6Xum0+V5midQEYqkN0nDlIuMKSEYHkjncMol9zGRVZOeOxX8eqfRz2uGlwdrSALQJubm9Zy5bWyFP8UGsYXSLpS868xDqWZMwnEc0sfDl4oUiabGzE8B7rMVE2cSlGXnBaUknNA4HE0A== X-Virus-Checked: Checked by ClamAV on apache.org --f46d043bd6faca06e504caa1a424 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've been having some success with the apr_memcache_* functions. In load-tests, however, I'm finding a lot of timeouts with apr_memcache_multgetp. Specifically, the status returned with the individual elements is APR_TIMEUP. This leads me to wonder what the significance of the second to last arg to this function is: apr_memcache_server_create( pool_, hosts_[i].c_str(), ports_[i], kDefaultServerMin, kDefaultServerSmax, thread_limit_, kDefaultServerTtlUs, &server); I have kDefaultServerSmax initialized to 600, as that's the value I found in mod_socache_memcache.c But that seems stingy (if it's really in microseconds). Should I be giving that a few hundred millis instead? http://apr.apache.org/docs/apr-util/1.4/group___a_p_r___util___m_c.html#ga18ddd72bc1ab5edb0a08a8f26f193bd3 claims that means "time to live of client connection" but I don't understand what that phrase means exactly, or if it relates to the APR_TIMEUP returns I've been suffering from. My code is here; http://code.google.com/p/modpagespeed/source/browse/trunk/src/net/instaweb/apache/apr_mem_cache.cc -Josh --f46d043bd6faca06e504caa1a424--