On Jun 5, 2009, Daniel Berlin <dber...@dberlin.org> wrote: >> >> We can measure some of these things now. Some can even be measured >> objectively ;-)
> Do you have any of them handy (memory use, compile time with release > checking only, etc) so that we can start the public > argument^H^H^H^H^H^discussion? > ;) :-) I don't, really. Part of the guidance I expected was on what the relevant measures should be. I wouldn't want to decide that for myself, because I can't say for sure that I fully understand the concerns in people's minds, and I wouldn't want to spend a lot of time collecting irrelevant data, or data that might be perceived as biased because of my lack of experience with benchmarks. That said, I planned on collecting and presenting at least some data, but I ran out of time before the deadline I'd set for myself (must post before the summit), while working on addressing the various suggestions I'd received for the bug fixes and new features I recently submitted. So the question is, what should I measure? Memory use for any specific set of testcases, summarized over a bootstrap with memory use tracking enabled, something else? Likewise for compile time? What else? -- Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/ You must be the change you wish to see in the world. -- Gandhi Be Free! -- http://FSFLA.org/ FSF Latin America board member Free Software Evangelist Red Hat Brazil Compiler Engineer
