public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: ASSI <Stromeko@nexgo.de>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
	Jon Turney <jon.turney@dronecode.org.uk>,
	overseers@sourceware.org
Subject: Re: [Cygwin] package-grep on Sourceware
Date: Wed, 27 Nov 2019 19:38:00 -0000	[thread overview]
Message-ID: <20191127193804.GB1967@redhat.com> (raw)
In-Reply-To: <1810471.5kLSPG0ym2@gertrud>

Hi -

> [...] I would like to understand what characteristic of the workload
> you were trying to avoid as to me it looks like avoiding IO comes at
> a significant cost in either memory or CPU consumption (or both).
> [...]

CPU elapsed time primarily.  I restored the previous package-grep.cgi,
with the xargs parallelization speedup.  We'll just have to eat the
I/O cost (or rather, letting hundreds of megabytes squat the page
cache in RAM).  A malevolent enough grep regex could still take a long
time (produce many hits), but less bad than before.

- FChE

  reply	other threads:[~2019-11-27 19:38 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
2019-11-25 16:48   ` ASSI
2019-11-27 19:38     ` Frank Ch. Eigler [this message]
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=20191127193804.GB1967@redhat.com \
    --to=fche@redhat.com \
    --cc=Stromeko@nexgo.de \
    --cc=fche@elastic.org \
    --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).