Perl 6 - the future is here, just unevenly distributed

IRC log for #parrotsketch, 2014-07-09

| Channels | #parrotsketch index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
03:30 Util Understandable! I had to go offline before you came back. We can just talk in #parrot in the morning. Thanks for attending!
07:33 basiliscos joined #parrotsketch
12:13 ilbot2 joined #parrotsketch
12:13 Topic for #parrotsketch is now Post closed tickets in your report. | Note: This channel is for our weekly status meetings (Tuesdays at 19:30 UTC); you probably want #parrot instead. | irclog: http://irclog.perlgeek.de/
13:25 bluescreen joined #parrotsketch
13:54 basiliscos joined #parrotsketch
14:10 rurban1 joined #parrotsketch
14:59 bluescreen joined #parrotsketch
16:22 Chirag joined #parrotsketch
16:37 Chirag Util: Thanks! I will ask if I face issues with perl versioning
16:40 rurban Chirag: How is it going?
16:42 Chirag Hey! I am testing commits from RELEASE 2.7 - 2.8 to identify bad commits... my machine is really slow so havent completed bench on all of them as yet
16:42 Chirag Writing the report now
16:42 Chirag blog*
16:44 rurban But have you got a few good numbers already < 1%
16:45 rurban or do the seconds look unreliable?
16:45 Chirag oops.. my bad I thought I was replying to Util
16:45 Chirag haven't really analyzed all of them... just glanced over them
16:46 Chirag but they look reliable
16:47 Chirag I stopped at 1174be4513d244c8e3102cdf280d0e6d1c89e341  .. which is still part of 2.7
16:47 rurban good
16:48 Chirag let me put the data on a gist
16:48 Chirag we can analyze that and will put my machine on another overnight run
16:50 rurban yes. I'm a bit worried that your data will be as useless as mine
16:51 rurban And I cannot do more benchmarks until Friday, because I'm now release testing B::C
16:52 Chirag oh.. shouldn't we be looking for >1%?
16:52 Chirag https://gist.github.com/ZYROz/457b89653f27127fee4b
16:56 rurban huh, you got one 16% spike. numbers look better than mine. I'll filter out >1% to get better results.
16:58 Chirag how did you analyze it that way?
17:00 rurban egrep "^tag=|seconds time elapsed" log.bench-chirag-2.7-2.8 | perl -lane'BEGIN{$/="tag="}; $F[0]=~s/RELEASE_//; $F[0]=~s|rurban/|0|; print "$F[0]\t$F[1]\t$F[7]" if $F[1]' > log.bench-chirag-2.7-2.8.data
17:02 rurban the 14-15s parts are worrying me. maybe the 34s tests actually threw exceptions?
17:03 Chirag but I had made sure it printed everything
17:03 rurban can you check some >30s manually if they run properly?
17:03 Chirag sure
17:04 rurban https://github.com/parrot/parrot-bench/b​lob/master/log.bench-chirag-2.7-2.8.data
17:06 rurban You only got a 1GHz machine. I've got 3GHz. that's why yours hould be ~3x slower. 34s makes sense
17:06 rurban So the <20s runs do look suspicious
17:07 Chirag I ll check those too
17:07 rurban only 1-3 please
17:07 rurban I'll filter the <30s out I guess
17:08 rurban egrep "^tag=|seconds time elapsed" log.bench-chirag-2.7-2.8 | perl -lane'BEGIN{$/="tag="}; $F[0]=~s/RELEASE_//; $F[0]=~s|rurban/|0|; print "$F[0]\t$F[1]\t$F[7]" if $F[1] and $F[1]>30.0' > log.bench-chirag-2.7-2.8.data.1
17:09 rurban egrep "^tag=|seconds time elapsed" log.bench-chirag-2.7-2.8 | perl -lane'BEGIN{$/="tag="}; $F[0]=~s/RELEASE_//; $F[0]=~s|rurban/|0|; print "$F[0]\t$F[1]\t$F[7]" if $F[1] and $F[1]>30.0 and $F[7] =~ /^0\./' > log.bench-chirag-2.7-2.8.data.1
17:12 Chirag 73/150 .. remaining suspicious?
17:18 rurban1 joined #parrotsketch
17:22 Chirag the 34.* seem to produce similar data .. checking <20
17:22 rurban https://github.com/parrot/parrot-bench​/blob/master/parrot-bench-2.7-2.8.png
17:23 rurban so there are 2 spikes to investigate
17:23 rurban but not really interesting. not the big slowdown so far
17:24 Chirag gc4729e2
17:24 Chirag hmm.. what about <20s ones?
17:24 rurban remove the first g and use it like git show c4729e2
17:25 Chirag ok
17:25 rurban c4729e2 is just a whitespace fix
17:25 rurban no idea about the <20s yet
17:25 Chirag then the one before - 4585a67
17:27 Chirag confirmed - they are incorrect.. for instance, b984a2c= 14.948903834 , now 34.880759557
17:45 Chirag rurban: So, should I retest <20s commits again? followed by the remaining commits?
18:09 rurban I see no benefit for retesting. you should rather find the slow down further the road towards 2.7. 2.7.0 should be something like 33s and suddenly it became slower (34s)
18:09 rurban oops, wrong channel, let's switch over to #parrot

| Channels | #parrotsketch index | Today | | Search | Google Search | Plain-Text | summary