Re: Performance Tracker project update

2008-01-24 Thread Erik Cederstrand
Alexander Leidinger wrote: Quoting Kris Kennaway <[EMAIL PROTECTED]> (from Thu, 24 Jan 2008 12:08:07 >> I don't see machine availability being a problem once we are ready to "take this live". Me too, but it's in the development stage and Robert asks for some new features, and I've read the a

Re: Performance Tracker project update

2008-01-24 Thread Alexander Leidinger
Quoting Kris Kennaway <[EMAIL PROTECTED]> (from Thu, 24 Jan 2008 12:08:07 +0100): Erik Cederstrand wrote: Alexander Leidinger wrote: In case you have some space left for more machines, maybe someone is willing to help out by sponsoring some. Just tell us how many machines you can hand

Re: Performance Tracker project update

2008-01-24 Thread Kris Kennaway
Ivan Voras wrote: Kris Kennaway wrote: Erik Cederstrand wrote: Ivan Voras wrote: I have a suggestion to make the graphs more readable: if a long period was chosen by the user (e.g. > 100 days / plot points), don't plot points and error bars, plot a simple line through the points. Also, set all

Re: Performance Tracker project update

2008-01-24 Thread Ivan Voras
Kris Kennaway wrote: > Erik Cederstrand wrote: >> Ivan Voras wrote: >>> >>> I have a suggestion to make the graphs more readable: if a long >>> period was chosen by the user (e.g. > 100 days / plot points), don't >>> plot points and error bars, plot a simple line through the points. >>> Also, set a

Re: Performance Tracker project update

2008-01-24 Thread Ivan Voras
Erik Cederstrand wrote: > I haven't touched malloc.conf but realize that I should. What's the > official recommendation on malloc settings? You'd have to patch /usr/src/lib/libc/stdlib/malloc.c and define MALLOC_PRODUCTION. Yes, it's not elegant. signature.asc Description: OpenPGP digital sig

Re: Performance Tracker project update

2008-01-24 Thread Kris Kennaway
Erik Cederstrand wrote: Alexander Leidinger wrote: In case you have some space left for more machines, maybe someone is willing to help out by sponsoring some. Just tell us how many machines you can handle (space/power/...) and if you are interested that we put it up on our wantlist. I'm s

Re: Performance Tracker project update

2008-01-24 Thread Kris Kennaway
Erik Cederstrand wrote: Ivan Voras wrote: I have a suggestion to make the graphs more readable: if a long period was chosen by the user (e.g. > 100 days / plot points), don't plot points and error bars, plot a simple line through the points. Also, set all date strings on the X-axis to empty

Re: Performance Tracker project update

2008-01-24 Thread Erik Cederstrand
Ivan Voras wrote: I have a suggestion to make the graphs more readable: if a long period was chosen by the user (e.g. > 100 days / plot points), don't plot points and error bars, plot a simple line through the points. Also, set all date strings on the X-axis to empty strings except for the da

Re: Performance Tracker project update

2008-01-24 Thread Erik Cederstrand
Alexander Leidinger wrote: In case you have some space left for more machines, maybe someone is willing to help out by sponsoring some. Just tell us how many machines you can handle (space/power/...) and if you are interested that we put it up on our wantlist. I'm sharing an office with 4 o

Re: Performance Tracker project update

2008-01-24 Thread Borja Marcos
On Jan 23, 2008, at 12:44 PM, Kris Kennaway wrote: One suggestion I have is that as more metrics are added it becomes important for an "at a glance" overview of changes so we can monitor for performance improvements and regressions among many workloads. One

Re: Performance Tracker project update

2008-01-24 Thread Alexander Leidinger
Quoting Erik Cederstrand <[EMAIL PROTECTED]> (from Wed, 23 Jan 2008 21:59:42 +0100): Finally, in the interests of making your life more complicated, it would be neat to graph performance across a set of FreeBSD branches overlaid or vertically offset so you could monitor, say, MySQL per