Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 41C49200C8C for ; Tue, 6 Jun 2017 13:55:20 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 40464160BC6; Tue, 6 Jun 2017 11:55:20 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7E128160BC3 for ; Tue, 6 Jun 2017 13:55:19 +0200 (CEST) Received: (qmail 68582 invoked by uid 500); 6 Jun 2017 11:55:18 -0000 Mailing-List: contact dev-help@thrift.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@thrift.apache.org Delivered-To: mailing list dev@thrift.apache.org Received: (qmail 68424 invoked by uid 99); 6 Jun 2017 11:55:17 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jun 2017 11:55:17 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id B2333E0061; Tue, 6 Jun 2017 11:55:17 +0000 (UTC) From: mfrawley To: dev@thrift.apache.org Reply-To: dev@thrift.apache.org References: In-Reply-To: Subject: [GitHub] thrift issue #1283: THRIFT-4218: Set TCP_NODELAY for PHP client socket Content-Type: text/plain Message-Id: <20170606115517.B2333E0061@git1-us-west.apache.org> Date: Tue, 6 Jun 2017 11:55:17 +0000 (UTC) archived-at: Tue, 06 Jun 2017 11:55:20 -0000 Github user mfrawley commented on the issue: https://github.com/apache/thrift/pull/1283 I'd just like to add that we deployed a similar fix to this on our infrastructure at Jimdo which led to this PR. We have a large PHP codebase which communicates with some services over Thrift. We support ~20 million websites and our logging and metrics indicate fewer timeouts after this change. We had tried several other tweaks previously and this seems to have had a bigger effect than raising the read/write timeouts (at least by a conservative amount). --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---