Re: [gstreamer] Enabling binary cache (instead of the xml one)

[Koen Kooi <k.kooi@student.utwente.nl>]

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:~#