From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Jan-Simon Möller" <dl9pf@gmx.de>,
bitbake-devel <bitbake-devel@lists.openembedded.org>,
"Joshua Watt" <JPEWhacker@gmail.com>,
"Michael Halstead" <mhalstead@linuxfoundation.org>
Subject: Re: [bitbake-devel] hashserv performance issues
Date: Thu, 23 May 2024 11:45:34 +0100 [thread overview]
Message-ID: <0c683b38268d46aa4a1f221ede72ba0ea61c1fb9.camel@linuxfoundation.org> (raw)
In-Reply-To: <3558580.dWV9SEqChM@arbeit>
On Thu, 2024-05-23 at 12:11 +0200, Jan-Simon Möller wrote:
> I share your concern ... and also with an eye on PRServ then.
> If we solve this here, we should apply the same lesson there.
>
> Can we rethink this maybe:
> - both are "microservices"
> - both are serving data stored in a (maybe even distributed) db
> - both need the concept of an upstream server (or even servers?) to
> 'federate'
>
> Essentially these bits should be a common codebase and the APIs a
> frontend to that. Otherwise we will learn lessons twice the hard way
> and have to write more code.
PRServ does not have a problem here, it isn't called in
parsing/runqueue codepaths and isn't tightly looped.
We've talked about the above issues on calls and we still need to
convince Joshua of the need and come up with a plan, along with someone
to do the development work. I'd like to understand Joshua's concerns
and find a way to alleviate them.
> For the performance issue ...
> would a local hashserv + upstream hashserv connection help ?
> Or do we need to query things 'always' anyway up to the upstream ...
I doubt unfortunately since it would still need to pass queries through
to the upstream. Geo specific servers may help and was our original
plan for this but we've been struggling with time for the setup.
> I'm willing to help, but would start on the deployment side as thats
> my immediate need as we disabled hashserv with scarthgap and want it
> back. Once this is up I can work my way down to code.
See above, I'd be happy to see work in that area but from the project
perspective, the performance issue is effectively blocking builds :(.
Cheers,
Richard
prev parent reply other threads:[~2024-05-23 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17D1D17091A0A935.11581@lists.openembedded.org>
2024-05-22 13:17 ` [bitbake-devel] hashserv performance issues Richard Purdie
2024-05-23 10:11 ` Jan-Simon Möller
2024-05-23 10:45 ` Richard Purdie [this message]
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=0c683b38268d46aa4a1f221ede72ba0ea61c1fb9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=JPEWhacker@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=dl9pf@gmx.de \
--cc=mhalstead@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.