15:01:35 #startmeeting Power management for Fedora 15:01:35 Meeting started Thu Sep 17 15:01:35 2009 UTC. The chair is skalnik1. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:35 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:58 Hello and welcome everybody 15:02:18 I'd like to start one line recap of last week 15:02:34 hello 15:02:40 #topic Last week recap 15:03:34 I was as a pm team member on irc alone 15:04:28 Phil Knirsch was on vacation the same this week 15:04:57 The other people were on Development Conference here in Brno 15:06:08 I informed about PM activity on the conference and I promised to provide info about 'watt hunting' competition 15:06:22 My promise is on the way :-) 15:07:03 it should be available on our SIG sites next week and I'll put the link here next week 15:07:14 well, what today 15:07:46 #topic Test and results 15:08:43 jvcelak did comparison test of scomes results for 32 and 64 bits 15:08:45 os 15:09:21 he prepares report of this test 15:09:32 this will be on SIG too 15:10:02 I'd like to mention shortly, that the test was done in virtual box 15:10:47 why not in kvm? 15:11:15 his choice 15:11:38 scomes results discover more ticks (~5 %) in 64 bit system 15:12:04 i/o operations was almost the same (a bit effective 64 bit system) 15:12:33 ok. but it we want use scomes for meassuring on virtual system, we will probably use kvm as fedora default 15:12:56 ok 15:13:35 i think it will be also interesting information to compare virtbox and kvm 15:13:41 yes 15:14:19 how many times did he measure one example? 15:15:15 i'm not able to answer now but i asked him for writting this info into report 15:16:02 ok 15:16:04 there will be complete description of the test + results 15:16:44 great 15:17:16 i started to test influence of compiz on system load 15:17:40 this was only the first attempt and i didn't prepare test enough 15:17:50 the results was the same 15:17:57 for comiz on and off 15:18:08 i tested it with bltk + open office 15:18:43 the problem is that the features of compiz are not used enough to be seen 15:19:33 quite more important test is doing jvcelak - live cd for test day 15:19:45 but we have no results till now 15:20:07 therefore i'd like to open a discussion how to continue 15:20:26 I suppose compiz doesn't consume more energy when you don't move windows etc. which doesn't move with bltk... 15:21:10 marcela: yes, therefore i wrote i didn't prepare test enough 15:21:39 ok 15:21:56 but i'm not sure if bltk provides enough features to simulate win moving etc. 15:24:05 does it use only keybord shortcuts? 15:25:29 i can move window in kde only by keyboard - alt-F3 and move with cursor keys 15:25:29 probably yes, i didn't see any usage of window handling 15:25:35 in the scenario 15:26:06 the bash scripts uses some utility 15:26:23 i have to investigate it a bit 15:26:26 do we have some output with differences from bltk? 15:26:51 I'd rather don't create new profile before we have some results from previous measurement 15:27:30 i have a set of results 15:27:36 great 15:28:31 i used bltk with office workload 15:28:55 each of situations was tested for 48 min 15:29:28 the results contains wifi on & off 15:29:50 wifi test was repeated for various state of battery 15:30:34 this means test started when battery is fully charged and then the battery capacity is 60% 15:31:06 there was no difference 15:31:38 then i tested wifi in two distances between laptop and ap 15:32:33 signal strenght 97% and ~50% 15:32:40 no difference 15:33:23 i plat to prepare test when the wifi will transfer some date but i have to eliminate other system activity (no writting to disk etc.) 15:35:42 ok when we have some differences we can prepare some new profiles, maybe. 15:36:03 yes 15:36:42 OT I have note to developer documentation - the man who works on it is ddomingo, so we should write to him these kind of notes 15:40:13 mracela, really ddomingo? 15:41:52 yeah 15:45:53 what about Test Day - I've started writing test examples 15:46:02 I suppose it will be ready for Test Day 15:46:58 great, i asked jscotka about inventory of test cases from last test day 15:47:26 he did it and he should find a time to help us this week 15:48:00 what about scomes testing? 15:48:50 who does the testing with scomes? 15:49:07 we will test if scomes does same results on different systems 15:50:06 tests like measure rpmbuild of package should has almost same number or read/written bytes, syscall and so 15:51:02 i'll prepare some cases with jhutar next week 15:51:46 ok 15:53:32 plautrba: jscotka is ready to help 15:55:03 ok 15:55:41 dpravec prepared test day site then we should move all info there: http://fedoraproject.org/w/index.php?title=Test_Day:2009-10-22 15:56:56 it looks good 15:57:33 let's summarize what is needed for next week 15:59:47 1. jvcelak will publish test report that is important for scomes test case 16:00:57 2. ivana promised putting info about competition on SIG 16:01:41 3. marcela will continue in test case for test day - is it, ok? 16:02:35 aye 16:02:40 4. plautrba + jhutar will work on test case for scomes 16:02:50 jscotka will help us 16:03:14 5. i'll take care about test day sites 16:03:41 6. then i'll contact last test day attendees 16:04:00 i suppose this is enough and our time slot is over 16:04:23 then any remarks? 16:04:37 no 16:04:48 no 16:05:03 so thanks everyone for joining and his activity and next week again with phil 16:05:10 #endmeeting