Re: [codesprints] Performance oriented codesprint before IETF 112
Robert Sparks <rjsparks@nostrum.com> Thu, 07 October 2021 19:43 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44E273A0DFC; Thu, 7 Oct 2021 12:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level:
X-Spam-Status: No, score=-2.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9cvJKsImEVEW; Thu, 7 Oct 2021 12:43:25 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0083E3A0DF7; Thu, 7 Oct 2021 12:43:24 -0700 (PDT)
Received: from unformal.localdomain ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 197JhNTr006008 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 7 Oct 2021 14:43:23 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1633635804; bh=A1dcWMvLxE8RxkQZ/Ld4YFw/xc6N2LEmALC1vMHSpQs=; h=From:To:Cc:References:Subject:Date:In-Reply-To; b=nsfyAKprwc/mNrvcHvSZ9DNd6nhtgyyOH+v+P/1BAraefw1gf/OXuOM5L81SrqrlY m6VSKwVO7k/ASdtZFT4iqJF4ddI63ZMpvsWP6VCGA7c21g0uiDFfLT1u03eOq9ulyM XQOJvj3LADYS4OUnybKNKFns6VU5Fs6Vzi02Wa6E=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be unformal.localdomain
From: Robert Sparks <rjsparks@nostrum.com>
To: tools-discuss <tools-discuss@ietf.org>
Cc: IETF Codesprints <codesprints@ietf.org>
References: <0d8472cb-179a-fb4c-ff7a-d6ec418b50d4@nostrum.com>
Message-ID: <a22535f4-f3d6-5c00-7f53-dbaad8f99a54@nostrum.com>
Date: Thu, 07 Oct 2021 14:43:18 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <0d8472cb-179a-fb4c-ff7a-d6ec418b50d4@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/codesprints/VP_LYf_PMBmBloISxSsaVMogVeM>
Subject: Re: [codesprints] Performance oriented codesprint before IETF 112
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/codesprints/>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2021 19:43:44 -0000
Given the doodle results, my plan is to have the primary sprint 27 Oct 1600-2000 UTC. People can join or leave as convenient. Coordinates will be sent soon. I will also have a conference set up for 28 Oct at those same times for followup and for anyone who can't participate on the 27th. I plan to make resources for analyzing performance available well before the sprint. Future communication on that topic will occur on the codesprints@ list. (If you are interested, please subscribe). RjS On 9/29/21 5:23 PM, Robert Sparks wrote: > We would like to hold a codesprint before IETF 112 focused on > datatracker performance. > > We have been improving the instrumentation of the datatracker, and > plan to provide quite a bit of information that will help us focus on > places that will help us most. These include statistic from the > database engine itself, and instrumentation that measures which views > are getting the most use, suffering the worst cumulative performance, > and how those views use the database. > > I expect much of the work will be verifying that the database has the > right indices, adjusting views to make better use of the ORM (such as > prefetching data (and not to prefetch too _much_ data), and adjusting > models where the current models are proving to be problematic. > > I have a doodle for two different possible times on either Oct 27 or > Oct 28. > > If you would like to participate, please add yourself to the doodle. > If the proposed times can't be made to work for you and you would > really like to engage in this kind of sprint, please just add a > comment at the doodle page. > > RjS > > > >
- [codesprints] Performance oriented codesprint bef… Robert Sparks
- Re: [codesprints] Performance oriented codesprint… Robert Sparks
- Re: [codesprints] Performance oriented codesprint… Robert Sparks