On 2014-04-30, 9:41 AM, David Rajchenbach-Teller wrote:
On 30/04/14 15:40, Gavin Sharp wrote:
I thought the "performance problems" in question were related to memory
use/worker initialization. But
https://bugzilla.mozilla.org/show_bug.cgi?id=981085#c0 doesn't really
have any useful detail.
Ehsan, what needs were you referring to there, and are they tracked in bugs?
Gavin
I believe that the problem was an actual bug in OS.File for B2G, which
has since then been fixed.
That was one of the issues. The other issues are:
1. OS.File uses a JS ChromeWorker which requires an unacceptable amount
of memory on b2g, on Tarako specifically.
2. Performance: OS.File's performance on b2g was apparently worse than
the XPCOM I/O function, it seems. I'm curious to know which device you
ran the benchmarks on, and what the benchmarks actually tested. It
could be that those performance issues have been fixed since the last
time people looked at things. FWIW for this use case an interesting
benchmark would be the performance of read operations of app manifest
JSON files.
I don't think that there are specific bugs on file for either one of the
two problems above.
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
