public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@elastic.org>
To: ASSI <Stromeko@nexgo.de>
Cc: Jon Turney <jon.turney@dronecode.org.uk>, overseers@sourceware.org
Subject: Re: [Cygwin] package-grep on Sourceware
Date: Mon, 25 Nov 2019 00:37:00 -0000	[thread overview]
Message-ID: <20191125003701.GB1093554@elastic.org> (raw)
In-Reply-To: <24997709.IERGFR1AUN@gertrud>

Hi -

> you've made changes to the package-grep CGI script on sourceware
> that pretty much remove its originally intended functionality.  The
> original was searching the index of the package _contents_ as it
> would get installed on the disk, while the JSON file you search now
> only has the metadata for the packages.  That's not even
> superficially the same thing.  [...]

OK.  As you may be aware, this simplification was done because the
previous code's workload was too high (grepping through 600MB+ of text
per cgi call), and we at overseers@ weren't told otherwise.


> I've looked into what could be done to do that in a more
> server-friendly way, but it turns out that there either isn't
> anything that's ready-made for this or I can't find it. [...]

Thanks for looking into it.  A few other possibilities to
ameliorate the impact of restoring the previous version:

- using xargs grep to use our extra cores, to reduce latency
- to impose a mod_qos concurrency limit on package-grep.cgi


- FChE

       reply	other threads:[~2019-11-25  0:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <24997709.IERGFR1AUN@gertrud>
2019-11-25  0:37 ` Frank Ch. Eigler [this message]
2019-11-25 16:48   ` ASSI
2019-11-27 19:38     ` Frank Ch. Eigler
2019-12-08 11:05       ` ASSI

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191125003701.GB1093554@elastic.org \
    --to=fche@elastic.org \
    --cc=Stromeko@nexgo.de \
    --cc=jon.turney@dronecode.org.uk \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).