Of course additions to libraries add ram & program memory. This however does not necessarily reflect efficiency of the library in a running circuit. Sometimes using more ram can increase speed. It also does not reflect additional features, or usefulness of the library.
The only stats that are good from this is to know how much memory you are using, if that is what is most important to you. For others, speed or functionality is most important. Matt. On Mar 13, 4:13 am, Sebastien Lelong <[email protected]> wrote: > Hi Joep, > > For now that's just compiler output parsing, my first idea was to checkout > jallib revisions at each compiler release (just before, just after) and give > comparison. This could give insight about home it performs globally (amongst > the ten sample I tried, 2.4o-beta saves several bytes of program memory and > eat few bytes of data memory). > > I'm also willing to compare what's comparable, maybe from a functional point > of view. Ex: GLCD refactoring, after converting libs and samples, how much > bytes did we loose/gain ? I'm not sure we can have a proper overview for > this kind of comparison, but without something to dig, we'll never know :) > On the side, I'm sure there are interesting things to extract, not given a > single point in time (eg. refactoring), but amongst a period of time. > > I'm planning to add some alert features: if program is 10% bigger, raise an > alarm. I'm also not sure yet how to display results. Ultimately I could > integrate it to buildbot if we find something trackable. > > Cheers, > Seb > > 2011/3/12 Joep Suijs <[email protected]> > > > > > > > Interesting! What would it take to run this on older svn revisions. > > This would give metrics of the past. Maybe collect metrics on each > > release? > > > Joep > > > 2011/3/11 <[email protected]>: > > > Revision: 2515 > > > Author: sebastien.lelong > > > Date: Fri Mar 11 07:55:22 2011 > > > Log: monitor: display comparison results from compiling different files > > > using different compiler, could be used to track metrics regarding how > > > jallib/jalv2 could become greedy... > > >http://code.google.com/p/jallib/source/detail?r=2515 > > > > Modified: > > > /trunk/tools/jallib.py > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "jallib" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group at > > >http://groups.google.com/group/jallib?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "jallib" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/jallib?hl=en. > > -- > Sébastien Lelonghttp://www.sirloon.nethttp://sirbot.org- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
