From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 8C5661F453; Mon, 21 Jan 2019 08:02:47 +0000 (UTC) Date: Mon, 21 Jan 2019 08:02:47 +0000 From: Eric Wong To: meta@public-inbox.org Subject: Re: [PATCH] solver: initial Perl implementation Message-ID: <20190121080247.qv4zkzk4krrljkb5@dcvr> References: <20190115084654.16254-1-e@80x24.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190115084654.16254-1-e@80x24.org> List-Id: Eric Wong wrote: > This will lookup git blobs from associated git source code > repositories. If the blobs can't be found, an attempt to > "solve" them via patch application will be performed. Still working on this... applying a 50+ patches (via index) can take over a second on a decent machine (so several seconds on a cheap VPS). Totally unacceptable with _other_ clients. So it needs to be broken out similar to how giant mbox streaming is implemented... It won't make the actual response faster, but it keeps things fair to other clients. Unlike the getline-based stuff; I can't do this in a PSGI-generic manner while returning proper HTTP status codes. So the current implementation remains for generic PSGI use; but I'll be reusing the public-inbox-httpd-specific scheduling stuff used for fronting git-http-backend...