Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9E1041023D for ; Sat, 23 Nov 2013 18:41:44 +0000 (UTC) Received: (qmail 82854 invoked by uid 500); 23 Nov 2013 18:41:44 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 82810 invoked by uid 500); 23 Nov 2013 18:41:44 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 82802 invoked by uid 99); 23 Nov 2013 18:41:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Nov 2013 18:41:44 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [71.6.165.248] (HELO kramer.ogre.com) (71.6.165.248) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Nov 2013 18:41:38 +0000 Received: from [10.244.26.77] (mobile-166-137-185-170.mycingular.net [166.137.185.170]) (authenticated bits=0) by kramer.ogre.com (8.14.5/8.14.5) with ESMTP id rANIeKGs012246 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 23 Nov 2013 10:41:16 -0800 References: <24DB4B81-4198-4F1C-B28F-72F4A4CD6DBE@apache.org> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: multipart/alternative; boundary=Apple-Mail-9869BE97-5BF8-4EE5-A3CF-FDA5A7A8E7AF Content-Transfer-Encoding: 7bit Message-Id: Cc: "users@trafficserver.apache.org" X-Mailer: iPhone Mail (11B554a) From: Leif Hedstrom Subject: Re: Curious about proxy.config.remap.num_remap_threads Date: Sat, 23 Nov 2013 11:41:15 -0700 To: Mark Moseley X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-9869BE97-5BF8-4EE5-A3CF-FDA5A7A8E7AF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable > On Nov 23, 2013, at 12:13 AM, Mark Moseley wrote: >=20 >> On Fri, Nov 22, 2013 at 7:51 PM, Leif Hedstrom wrote: >>=20 >> On Nov 22, 2013, at 11:18 AM, Mark Moseley wrote:= >>=20 >> > I'm looking to deploy ATS in a very busy, remap-heavy reverse proxy env= ironment. I'll be using a handful of lines of Lua to remap based on an incom= ing header. >> > >> > The new proxy.config.remap.num_remap_threads option sounds like it'd be= pretty important to set for such a scenario. >> > >> > Could the devs chime in on what would be an appropriate # for this sett= ing? >> > >> > Should 1 suffice? Should it be equal to # of cores? Or something much h= igher? >>=20 >>=20 >> The only use case I think think of for the remap threads feature is if yo= u have a plugin that can block a thread. With block, I mean, not yield it in= some reasonable amount of milliseconds. For now, if you use this remap thre= ads processor, you also have to turn off the per thread sharing of sessions,= and switch to a single global session pool. >=20 >=20 > Ok, so it sounds like if something isn't blocking, then there's no need to= set it at all then. My Lua code is just doing some munging on the original d= estination IP, so should never block. Sound right?=20 Right. -- Leif=20= --Apple-Mail-9869BE97-5BF8-4EE5-A3CF-FDA5A7A8E7AF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit


On Nov 23, 2013, at 12:13 AM, Mark Moseley <moseleymark@gmail.com> wrote:

On Fri, Nov 22, 2013 at 7:51 PM, Leif Hedstrom <zwoop@apache.org> wrote:

On Nov 22, 2013, at 11:18 AM, Mark Moseley <moseleymark@gmail.com> wrote:

> I'm looking to deploy ATS in a very busy, remap-heavy reverse proxy environment. I'll be using a handful of lines of Lua to remap based on an incoming header.
>
> The new proxy.config.remap.num_remap_threads option sounds like it'd be pretty important to set for such a scenario.
>
> Could the devs chime in on what would be an appropriate # for this setting?
>
> Should 1 suffice? Should it be equal to # of cores? Or something much higher?


The only use case I think think of for the remap threads feature is if you have a plugin that can block a thread. With block, I mean, not yield it in some reasonable amount of milliseconds. For now, if you use this remap threads processor, you also have to turn off the per thread sharing of sessions, and switch to a single global session pool.


Ok, so it sounds like if something isn't blocking, then there's no need to set it at all then. My Lua code is just doing some munging on the original destination IP, so should never block. Sound right?

Right.

-- Leif 
--Apple-Mail-9869BE97-5BF8-4EE5-A3CF-FDA5A7A8E7AF--