Re: [e-users] Eet compared with JSON - Eet comes out on top
On Wed, 21 Aug 2013 08:27:10 -0300 Gustavo Sverzut Barbieri said: > > > On 21/08/2013, at 08:03, Carsten Haitzler (The Rasterman) > 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. > > Great, in Tizen list (can't remember which) they were saying that qt5 json is > way faster than json-c, could you try it as well? Then I can send them the > links :-) oh.. and then i have to get qt5 installed. compile it.. or find a ppa... as well as figure out the qjasondocument thing... enough of my day used up already :) > > -- > > - Codito, ergo sum - "I code, therefore I am" -- > > The Rasterman (Carsten Haitzler)ras...@rasterman.com > > > > > > -- > > 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 > > -- > 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 > -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- 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
Re: [e-users] Eet compared with JSON - Eet comes out on top
On Wed, 21 Aug 2013 08:27:10 -0300 Gustavo Sverzut Barbieri said: > > > On 21/08/2013, at 08:03, Carsten Haitzler (The Rasterman) > 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. > > Great, in Tizen list (can't remember which) they were saying that qt5 json is > way faster than json-c, could you try it as well? Then I can send them the i already spent enough of my day with libjson... i assume they have figures on how much faster qt is compared to libjson (2x? 3x? 5x?). :) then the numbers should be roughly comparable. :) > > -- > > - Codito, ergo sum - "I code, therefore I am" -- > > The Rasterman (Carsten Haitzler)ras...@rasterman.com > > > > > > -- > > 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 > > -- > 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 > -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- 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
Re: [e-users] Eet compared with JSON - Eet comes out on top
On Wed, 21 Aug 2013 20:03:41 +0900 Carsten Haitzler (The Rasterman) 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.9% 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
[e-users] Enlightenment Developer Day - 2013
https://phab.enlightenment.org/phame/live/3/post/enlightenment_developer_day_2013/ It's on Again - 20th of October, Edinburgh, Scotland We're pleased to announce that Developer Day is on again this year. It will be co-hosted alongside Linuxcon Europe Which will be held on October 21-23. We'd like to thank Samsung Electronics for financially supporting this event and making it happen. You will need to register for the Linuxcon conference, and optionally pay to attend that event. Please see the Linuxcon Europe site for more information about venue, accommodation and pricing. This year we will be asking for a small registration fee for Developer Day that will be put towards hosting all registered attendees for an end-of-day dinner and drinks, so assume your money is being well spent in feeding and watering you for the night. The day will be a full day of presentations, panels, discussions and the ability for developers and users to get together face-to-face, present the state of things and where they are going, ask questions, propose ideas and otherwise have a jolly good time. At this point we'd like to call for anyone wanting to present or participate to register their interest by filling out their name and proposal on 2013 Developer Day Page More details on how to register, exact venue location as well as the schedule for the day will be posted soon. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- 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
Re: [e-users] Eet compared with JSON - Eet comes out on top
On 21/08/2013, at 08:03, Carsten Haitzler (The Rasterman) 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. Great, in Tizen list (can't remember which) they were saying that qt5 json is way faster than json-c, could you try it as well? Then I can send them the links :-) > > -- > - Codito, ergo sum - "I code, therefore I am" -- > The Rasterman (Carsten Haitzler)ras...@rasterman.com > > > -- > 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 -- 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
[e-users] Eet compared with JSON - Eet comes out on top
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. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- 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