From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/2] support/scripts/pkg-stats: URL check using threads
Date: Wed, 3 Oct 2018 14:54:19 +0200 [thread overview]
Message-ID: <20181003145419.2f76fe63@windsurf> (raw)
In-Reply-To: <5bb4123cbed5b_6f723fa9ec08e7bc6558f@ultri5.mail>
Hello Ricardo,
On Tue, 02 Oct 2018 21:50:04 -0300, Ricardo Martincoski wrote:
> On Mon, Oct 01, 2018 at 11:37 PM, Matt Weber wrote:
>
> > Adds a pool of worker threads to accelerate connection testing.
> >
> > ~7.5MB and 2% CPU per thread on a Intel i5-3230M CPU @ 2.60GHz.
> >
> > Runtime is ~3min in parallel vs ~15min.
> >
> > CC: Ricardo Martincoski <ricardo.martincoski@gmail.com>
> > Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
>
> Reviewed-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
So this threading works for you? I think it is modeled after what I
initially did to retrieve the upstream version of the packages, and you
said it wasn't working well for you.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-03 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 2:37 [Buildroot] [PATCH v3 1/2] support/scripts/pkg-stats: URL checking support Matt Weber
2018-10-02 2:37 ` [Buildroot] [PATCH v3 2/2] support/scripts/pkg-stats: URL check using threads Matt Weber
2018-10-03 0:50 ` Ricardo Martincoski
2018-10-03 12:54 ` Thomas Petazzoni [this message]
2018-10-03 13:22 ` Ricardo Martincoski
2018-10-09 8:15 ` Thomas Petazzoni
2018-10-03 0:49 ` [Buildroot] [PATCH v3 1/2] support/scripts/pkg-stats: URL checking support Ricardo Martincoski
2018-10-09 8:15 ` Thomas Petazzoni
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=20181003145419.2f76fe63@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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