On Mon, 11 May 2009 12:28:58 -0300 Gustavo Sverzut Barbieri <[email protected]> said:
> On Mon, May 11, 2009 at 12:12 PM, Carsten Haitzler <[email protected]> > wrote: > > On Mon, 11 May 2009 11:31:54 -0300 Gustavo Sverzut Barbieri > > <[email protected]> said: > > > >> On Mon, May 11, 2009 at 10:10 AM, Enlightenment SVN > >> <[email protected]> wrote: > >> > Log: > >> > comments - man is that struct big! > >> > >> 1st - values are wrong from 64bits, use pahole and it will tell you > >> exactly. > > > > i know that! i was simply going over it as a bi-product of memory profiling > > and now that evas images are in mmaped shm segments from a server... they > > no longer are the nastiest alloc on the list! this one is pretty high up > > there. all pointers of course are double the size (8 bytes) in 64bit. > > > > what i am most concerned about is the space where memory really matters - > > embedded. where you have no swap. where you only have 32, 64 or 128m ram > > possibly... and here it's still 32bit. after some looking into that struct i > > think i can shave it down to < 100bytes (from 300 or so) and for e17 itself > > that means a good 150kb or so saving easily. > > > > i simply was making notes. > > > >> 2nd - that struct is really big, that's why I was suggesting using the > >> same thing as evas_object does and have there just the common fields > >> (geometry, visibility, ...) and custom/specialized fields in separate > >> struct. > > > > i know. thats what i as doing - but in detail. i was finding common members > > and grouping them and looking to see if it will be easy to have them > > dynamically allocated based on part type. :) at least runtime edje is no > > problem (just a chunk of renaming in lots of places and some changes to the > > allocation code). edje_editor tho might be a bit trickier. :) > > if you're at it, do it all in one alloc instead of evas that is 2 > layers, with common pointing to the specific. this would save a > pointer (not much really) and avoid memory to be less fragmented. that was my plan... -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
