|
Parrot 6.5.0 "Black-winged Lovebird" | parrot.org/ | Log: irclog.perlgeek.de/parrot | #parrotsketch meeting Tuesday 19:30 UTC Set by moderator on 9 July 2014. |
|||
|
01:38
FROGGS_ joined
04:32
estrabd joined
07:10
basiliscos joined
09:47
Psyche^ joined
13:21
bluescreen joined
13:43
basiliscos joined
13:58
kjs joined
14:01
kjs left
14:11
Chirag joined
14:14
bluescreen_ joined,
bluescreen joined
14:39
cooper joined
|
|||
| Chirag | rurban: gist.github.com/ZYROz/ffb7e8e87f1f3264f1d5 | 14:55 | |
| But I am not sure why it is missing 165-182 ; 127-136 | 14:57 | ||
| rurban | Do have an idea why 14s vs 24s ? | 15:01 | |
| 34s | |||
| and 2.7.0 has 35.2s which is slower than 2.8. No need to investigate this range if it got faster, not slower | 15:02 | ||
| Chirag | no.. the bench is the only process that ran throughout.. | ||
| it hasn't skipped branches in between right? | 15:03 | ||
| rurban | some branch merges were not linear, that's why | 15:04 | |
| see git topo | |||
| Chirag | oh i see | 15:05 | |
| rurban | git topo = log --oneline --topo-order --graph | ||
| Chirag | so I guess nothing to go on, right? | 15:39 | |
| rurban | well, you could check my range, there were several slowdowns. But not easy to find the real problems | 15:40 | |
| Chirag | hmm.. I can try 2.9 - 3.0 | 15:43 | |
| rurban | The rough timings are already there. you just need to check the git dsiff ranges, if something looks suspicious, and then redo the benchmark just for this range | 15:46 | |
| Chirag | will try to do that | 15:50 | |
|
16:25
FROGGS joined
|
|||
| rurban | ok, did my other releases, sigh. (should hold for a year or so I hope) | 17:02 | |
| Chirag | :) | 17:05 | |
|
18:15
bighugedog joined
18:44
bluescreen_ joined
18:45
bluescreen__ joined
21:36
rurban_ joined
21:58
davidfetter joined
22:15
kid51 joined
22:23
bluescreen joined
22:29
bluescreen_ joined
|
|||