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 On Wed, Apr 30, 2014 at 6:19 AM, David Rajchenbach-Teller < dtel...@mozilla.com> wrote: > I don't know of any performance problems for reading files with OS.File > at the moment. Actually, I benchmarked it and we are 2x-5x faster than > NetUtil at reading + decoding files, these days. > > Cheers, > David > > On 29/04/14 17:22, Nathan Froyd wrote: > > ----- Original Message ----- > >> The current best practice for file I/O in privileged JS is OS.File. It > >> has mechanisms for doing encoding conversion and compressing data. > >> That there is some b2g code using NetUtil/XPCOM instead is a bug, and > >> probably was caused by the relevant code being written prior to the > >> existence of OS.File (or it's doing something that OS.File doesn't > >> support, but I think that's unlikely now). > > > > Sometimes it's a deliberate decision because OS.File has performance > problems, see e.g. bug 981085. > > > > (The OS.File performance problems are of course bugs in their own right, > but sometimes it's not so easy to sort those out.) > > > > -Nathan > > _______________________________________________ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform > > > > > -- > David Rajchenbach-Teller, PhD > Performance Team, Mozilla > > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
