From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chris Larson <clarson@kergoth.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>,
poky <poky@lists.yoctoproject.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [bitbake-devel] Bitbake in server mode
Date: Wed, 21 Aug 2013 17:19:21 +0100 [thread overview]
Message-ID: <1377101961.25999.121.camel@ted> (raw)
In-Reply-To: <CABcZANnt4v4LoM+HnK_=6VMDgSCFR7qGfciMdpXxSQ+Gc4HBEA@mail.gmail.com>
On Wed, 2013-08-21 at 08:56 -0700, Chris Larson wrote:
>
> On Wed, Aug 21, 2013 at 7:26 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> Known issues:
>
> a) Parsing is slower. Probably due to all the debug messages
> going over
> the IPC/xmlrpc. UI event filtering should fix it.
> b) Something is causing a cache reparse initially. Need to
> figure out
> what. Maybe the BBSERVER variable itself?
>
> This is still development so I'd not recommend everyone use
> this for
> production just yet but it gives some nice insight into what
> the future
> holds!
>
> We should be able to make bitbake in this mode much more
> responsive to
> commands since there is no cache overhead.
>
> I expect the obvious question to be, what happens if a recipe is
> altered between starting the server and running a command :)
I should have been clearer, it will reparse, the normal cache checks
take effect, it just doesn't have to unpickle cache bits from disk which
is where the time is taken.
What happens if you edit recipes whilst bitbake is running a command? Do
not do that, just like today!
Cheers,
Richard
prev parent reply other threads:[~2013-08-21 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 14:26 Bitbake in server mode Richard Purdie
2013-08-21 15:56 ` [bitbake-devel] " Chris Larson
2013-08-21 16:19 ` 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=1377101961.25999.121.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@lists.yoctoproject.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