On Wed, 21 Aug 2013 20:03:41 +0900 Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote:
> > https://phab.enlightenment.org/phame/live/1/post/eet_compared_with_json_eet_comes_out_on_top/ > > --------------------------------------------------------- > Given the mainstream can't figure out what to use (XML, JSON... > what's next?), Eet manages to lead hands-down when compared to JSON > > Summary: > > Data files can be between 4 and 860 TIMES larger with JSON. > Cold read time for JSON is 10 TIMES slower than Eet. > Cold writes take 40% longer with JSON than with Eet. > Hot reads are 7 TIMES slower with JSON than with Eet. > Hot writes take 37% longer with JSON than with Eet. > > XML will be between 18 and 26 TIMES slower than Eet at loading config. > Cool, my money was on eet all along. It's why I want to use it for everything. Human readable formats are a bad idea when 99.99999% of the time, humans are not reading it. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
