Performance/Meetings/2008 09
Performance/Meetings/2009/09/18
Meeting Minutes
IRC Meeting of Sun Microsystems (StarOffice) with RedFlag2000 and the Community ??
Performance Project
Date: 2009/09/18
Time: 16:03– 16:52
Meeting No.:
Agenda:
(4:03:57 PM) liheng: hi,all
(4:03:58 PM) liheng: :)
(4:04:07 PM) mhu1: hi
(4:04:16 PM) liangjun: hi,all
(4:04:16 PM) liheng: Sorry,I'm late...
(4:04:38 PM) liheng: another meeting take the long time:)
(4:04:50 PM) mhu1: Don't worry about being late, usually I am the one who is late :-)
(4:05:46 PM) liheng: today, Guoys can't attend this meeting, because he is just tranning several new perpons:)
(4:06:19 PM) liheng: mhu:Did you receive the mail about this IRC
(4:06:21 PM) mhu1: well, training new people is good also, I think
(4:06:33 PM) mhu1: yes, I have read your email
(4:07:38 PM) liheng: please help us to find your code of T-Test, we will start to create analyzing tool
(4:08:51 PM) mhu1: yes, of course. If you give me a couple of minutes, I can look the code up....
(4:09:50 PM) liheng: Yes, today we have only one topic, what is develpor want to see in test report
(4:16:13 PM) mhu1: okay, I have found the code, but I need a couple more minutes, stay tuned ...
(4:17:14 PM) liheng: okay, maybe we can take a easy meeting today:)
(4:21:23 PM) mhu1: okay, I have sent the code attached as reply to your email. So, you should have it soon ...
(4:21:52 PM) liheng: Thank you every much!
(4:21:53 PM) liheng: ;)
(4:22:01 PM) mhu1: The code is somewhere between 3 and 5 years old, so I don't exactly remember all details.
(4:22:35 PM) mhu1: but the main function contains a "unit test" like example how to use it.
(4:23:12 PM) liheng: we study it first, for problems about it we discuss them via Email
(4:23:20 PM) mhu1: okay.
(4:24:16 PM) liheng: What do you think about what is develpor want to see in test reports?
(4:24:22 PM) mhu1: You were asking "what developer want to see in test report..." ...
(4:24:30 PM) liheng: yes :)
(4:24:38 PM) mhu1: (I just wanted to prepare an answer ...)
(4:25:15 PM) mhu1: So, what I think is most obvious, is "any change to better or worse".
(4:25:42 PM) mhu1: next question would be "change in what?"...
(4:27:09 PM) mhu1: and these what (the "Y" in our math. discussion, or "macroscopic observable values") can be "startup time", "document load time", "total memory consumption", or ...
(4:27:33 PM) liheng: any change to better or worse abou
(4:28:25 PM) mhu1: yes?
(4:28:27 PM) liheng: What i understand you is we must find and show some macroscopic values change
(4:28:56 PM) liheng: "(4:27:33 PM) liheng: any change to better or worse abou " is a worry type:(
(4:29:19 PM) mhu1: that is the "high level view" only, of course. But I think this what most people (definitely users) are interested in.
(4:30:13 PM) mhu1: okay, here are some thoughts...
(4:30:37 PM) liheng: yes, and then we must show the detail of change by X (microcosmic values)
(4:32:49 PM) mhu1: you developer work on some root cause "X" and work hard to improve the performance / time consumption / memory consumption of "X", and of course you expect it will improve the overall "Y" = "startup performance" (if Y=f(X)). So your "true" interest is to see that "Y" has indeed improved when you have been improving "X".
(4:33:43 PM) mhu1: ...and for you developer, of course changes in "X" are also important to be reported.
(4:33:52 PM) liheng: and, if you want to optimizing the code,do you have a prediction of effect
(4:34:22 PM) mhu1: ...but maybe not so important to other developers how are not working on "your X" but on "their X".
(4:37:34 PM) liheng: but I think we must show all X change to represent what has been really changed
(4:39:21 PM) mhu1: I was only thinking about the level of detail; yes, maybe it is also important to show to all what X have been worked on.
(4:39:55 PM) liheng: At first we can make some template for reports that mainly show the statistical results of macroscope value :)
(4:40:18 PM) liheng: And append more details step by step
(4:41:01 PM) mhu1: yes, that would be the place to start (like the CWS performance measurements that Malte did).
(4:41:50 PM) mhu1: and, it would show us, if we have the process under control (that is can do reliable and repeatable measurements).
(4:41:56 PM) liheng: To show all X is in order to show which changes cancel out your improving
(4:42:41 PM) mhu1: Ah, yes that is an important point; I think I tend to forget about that; you are right :-)
(4:43:55 PM) liheng: okay, that all for me:)
(4:44:43 PM) mhu1: okay; can you send a note when you have received my email with the source code?
(4:45:35 PM) liheng: yes, "DataAnalysis.java"
(4:45:36 PM) liheng: :)
(4:46:01 PM) mhu1: okay, so you already have it, that is good. Have fun with it.
(4:46:29 PM) liheng: By the way, the work of improving of configmgr is all in well:)
(4:46:42 PM) mhu1: it is stolen from the book "Numerical Recipes (Fortran edition)".
(4:47:24 PM) mhu1: oh yes, I wanted to ask that for some time; good to hear that you are making progress with configmgr.
(4:47:25 PM) liheng: I will try to find that book
(4:48:38 PM) mhu1: the book should not be necessary, only if you to understand the details of "incomplete gamma functions" and such; try to study the Main() function, how the T-Test is used, that should be sufficent.
(4:49:35 PM) mhu1: or a book about statistical data analysis (why you want to use a T-Test, and what it tells you)
(4:49:40 PM) liheng: The first vesion will be brought out in 3~4 weeks, becouse long holiday of National Day;)
(4:50:11 PM) mhu1: okay. When is that national holiday?
(4:50:58 PM) liheng: Sep 28th to Oct 5th:)
(4:51:18 PM) mhu1: Ah, okay. Wish you a good time then.
(4:51:38 PM) liheng: thank you and see you next week
(4:51:55 PM) mhu1: yes, see you next week. Bye all.
(4:52:18 PM) liheng: bye
