Yesterday we had a discussion on irc, if we should put abstract data types of ecore and of evas into a single standalone lib. The whole discussion came up because of the two implementations of the shared strings. And in fact if we really want to share strings efficient, we have to share them over the borders of the different libraries.
Raster's idea was to first put the shared string stuff in this new library because both implementation have the same api (of course the names are different) and the same functionality. Remains the question which implementation we use. Therefor I've written a small test application, to measure the time it takes to create new strings, access new strings and to delete them. You can find the program here: mowem.de/ecore/compare.c And here a here the plot of the result mowem.de/ecore/result_direct.ps In short words, since evas uses a static bucket count it has a very good performance for few strings, for many ecore has a good access time, but still pays the price for the reordering of the increased or decreased bucket count. Peter ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
