Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [gstreamer] Enabling binary cache (instead of the xml one)
Date: Sat, 15 Nov 2008 12:06:02 +0100	[thread overview]
Message-ID: <gfmaeq$mr9$1@ger.gmane.org> (raw)
In-Reply-To: <200811150004.50508.zecke@selfish.org>

On 15-11-08 00:04, Holger Freyther wrote:
> Hey Guys,
>
> I wonder if we have ever considered in using the experimental gstreamer
> feature to build it with "--enable-binary-registry".
>
> This is not changing the way the registry is working, the result is simply
> stored in binary and not xml. This avoids parsing on start.
>
> For devices like the neo (with incredible slow flash speed) avoiding stating
> all plugins would (changing the way the registry is working) would be a lot
> better...
>
> what do you think? Risk and use an experimental feature (it is using mmap so
> the risk of SIGBUS is there)

Is it using read-only mmap or read-write mmap? If it's the latter then 
people using jffs2 are out of luck :(

regards,

Koen

>
> 	z.
>
>
>
> Results of micro benchmark on my neo:
>
> Binary cache:
>
> # Building cache
> Total count: 119 plugins, 351 features
> real    0m 12.36s
> user    0m 5.71s
> sys 0m 5.72s
>
> # Cached
> Total count: 119 plugins, 351 features
> real    0m 1.74s
> user    0m 1.03s
> sys 0m 0.35s
>
>
> XML Cache:
> # Building cache
> Total count: 119 plugins, 351 features
> real    0m 16.42s
> user    0m 6.94s
> sys 0m 9.19s
>
>
> # Cached
> Total count: 119 plugins, 351 features
> real    0m 1.87s
> user    0m 1.28s
> sys 0m 0.41s
> root@om-gta02:~#





  parent reply	other threads:[~2008-11-15 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 23:04 [gstreamer] Enabling binary cache (instead of the xml one) Holger Freyther
2008-11-14 23:23 ` Leon Woestenberg
2008-11-15 11:06 ` Koen Kooi [this message]
2008-11-15 11:47 ` Michael 'Mickey' Lauer
2008-11-15 12:13 ` Phil Blundell

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='gfmaeq$mr9$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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