00:42:07  * toddynhoquit (Ping timeout: 240 seconds)
00:44:28  * plutoniixjoined
00:44:35  * plutoniixquit (Max SendQ exceeded)
00:46:04  * plutoniixjoined
00:47:07  * Net147quit (Read error: Connection reset by peer)
00:47:13  * plutoniixquit (Max SendQ exceeded)
00:47:39  * plutoniixjoined
00:50:33  * Net147joined
00:50:59  * toddynhojoined
01:34:06  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
01:42:27  * unixpicklejoined
01:42:57  * joyeejoined
01:47:09  * joyeequit (Ping timeout: 240 seconds)
02:15:05  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
03:01:36  * joyeejoined
03:05:31  * Net147quit (Read error: Connection reset by peer)
03:06:01  * joyeequit (Ping timeout: 240 seconds)
03:10:14  * Net147joined
03:35:43  * Guest59quit (Quit: My Mac has gone to sleep. ZZZzzz…)
03:51:09  * joyeejoined
03:55:31  * joyeequit (Ping timeout: 240 seconds)
04:27:39  * joyeejoined
04:38:45  * joyeequit (Remote host closed the connection)
04:48:42  * joyeejoined
04:53:28  * joyeequit (Ping timeout: 260 seconds)
06:57:06  * joyeejoined
07:01:30  * joyeequit (Ping timeout: 240 seconds)
07:08:47  * xiinotulpjoined
07:10:00  * xiinotulpquit (Max SendQ exceeded)
07:10:31  * xiinotulpjoined
07:59:31  * joyeejoined
08:04:00  * joyeequit (Ping timeout: 240 seconds)
09:07:41  * joyeejoined
09:09:03  <trungl-bot>Tree closed by buildbot@chromium.org: closed (/builders/V8%20Linux/builds/17281 from 3258b2690e1be50e2ab47722585ecfc29754a657)
09:11:54  * joyeequit (Ping timeout: 256 seconds)
09:28:11  <trungl-bot>Tree opened by machenbach@chromium.org: open
09:58:34  * xiinotulpquit (Ping timeout: 264 seconds)
09:58:53  * plutoniixquit (Ping timeout: 268 seconds)
10:25:11  * mylesborinsquit (Quit: farewell for now)
10:25:41  * mylesborinsjoined
10:26:23  * joyeejoined
10:31:04  * joyeequit (Ping timeout: 258 seconds)
11:26:03  * joyeejoined
11:30:28  * joyeequit (Ping timeout: 260 seconds)
11:40:39  * joyeejoined
11:47:43  * joyeequit (Read error: Connection reset by peer)
11:48:05  * joyeejoined
11:59:07  * joyeequit (Read error: Connection reset by peer)
12:01:23  * joyeejoined
12:11:11  * joyeequit (Read error: Connection reset by peer)
12:11:38  * joyeejoined
12:32:26  * joyeequit (Read error: Connection reset by peer)
12:32:56  * joyeejoined
12:44:07  * joyeequit (Read error: Connection reset by peer)
12:46:18  * joyeejoined
13:01:28  * joyeequit (Ping timeout: 240 seconds)
13:08:20  * unixpicklejoined
13:09:54  * plutoniixjoined
13:15:34  * joyeejoined
13:25:25  * bradleymeckjoined
13:27:15  * joyee_joined
13:27:24  * joyeequit (Read error: Connection reset by peer)
13:38:34  * joyeejoined
13:38:56  * joyee_quit (Read error: Connection reset by peer)
13:48:33  * joyeequit (Read error: Connection reset by peer)
13:49:10  * joyeejoined
13:56:21  * joyeequit (Read error: Connection reset by peer)
13:56:29  * joyeejoined
13:58:34  * joyeequit (Read error: Connection reset by peer)
13:58:58  * joyeejoined
14:09:48  * joyeequit (Read error: Connection reset by peer)
14:16:26  * joyeejoined
14:51:47  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
14:56:00  * unixpicklejoined
14:56:44  * Gettyquit (Ping timeout: 268 seconds)
14:56:56  * Gettyjoined
15:05:56  * bradleymeckquit (Read error: Connection reset by peer)
15:06:08  * bradleymeckjoined
15:07:58  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
15:09:20  <trungl-bot>Tree closed by buildbot@chromium.org: closed (/builders/V8%20Linux/builds/17293 from d73b11ecd205c405e0799d4487df3c151f4da56b)
15:09:49  <caitp>uh
15:09:56  <caitp>that CL broke the tree what?
15:12:21  <trungl-bot>Tree opened by machenbach@chromium.org: open
15:25:15  * unixpicklejoined
15:26:08  * joyeequit (Read error: Connection reset by peer)
15:26:26  * joyeejoined
15:38:01  * joyeequit (Read error: Connection reset by peer)
15:38:33  * joyeejoined
15:52:38  * plutoniixquit (Ping timeout: 260 seconds)
15:53:04  * bradleymeckquit (Quit: bradleymeck)
16:05:21  * plutoniixjoined
16:19:07  * joyee_joined
16:19:07  * joyeequit (Read error: Connection reset by peer)
16:29:19  * joyee_quit (Read error: Connection reset by peer)
16:29:48  * joyeejoined
16:32:47  * seventhjoined
16:37:15  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2010030309])
16:40:13  * joyeequit (Read error: Connection reset by peer)
16:40:37  * joyeejoined
16:47:25  * bradleymeckjoined
16:52:20  * joyee_joined
16:56:06  * joyeequit (Ping timeout: 240 seconds)
17:05:07  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
17:20:11  * plutoniixquit (Read error: Connection reset by peer)
17:24:16  * joyee_quit (Read error: Connection reset by peer)
17:24:44  * joyeejoined
17:34:31  * joyeequit (Read error: Connection reset by peer)
17:35:03  * joyeejoined
17:41:12  * plutoniixjoined
17:54:50  * unixpicklejoined
18:03:41  * joyee_joined
18:07:28  * seventhquit (Ping timeout: 246 seconds)
18:07:37  * joyeequit (Ping timeout: 260 seconds)
18:10:29  * joyee_quit (Read error: Connection reset by peer)
18:10:48  * joyeejoined
18:22:28  * joyeequit (Read error: Connection reset by peer)
18:23:04  * joyeejoined
18:33:29  * joyeequit (Read error: Connection reset by peer)
18:33:54  * joyee_joined
18:43:58  * joyeejoined
18:46:00  * joyeequit (Read error: Connection reset by peer)
18:46:23  * joyeejoined
18:47:30  <jwolfe>i thought --gerrit was the default for git cl upload. why did i think that?
18:47:59  * joyee_quit (Ping timeout: 268 seconds)
18:49:29  * seventhjoined
18:53:10  <caitp>I don't know, but the source code formatting in the polygerrit diffs is a lot easier to read than on rietveld
18:53:38  <caitp>so, thanks for using --gerrit
18:57:21  <jwolfe>the comment feed on gerrit is super bulky, but other than that, gerrit seems better than rietveld. i especially like that it tracks the commit the changes are based on.
18:57:43  * joyeequit (Read error: Connection reset by peer)
18:57:54  * joyeejoined
19:09:02  * joyeequit (Read error: Connection reset by peer)
19:09:44  * joyeejoined
19:17:52  * joyeequit (Read error: Connection reset by peer)
19:18:16  * joyeejoined
19:25:09  * joyeequit (Read error: Connection reset by peer)
19:25:19  * joyeejoined
19:31:38  * joyeequit (Read error: Connection reset by peer)
19:31:44  * joyeejoined
19:36:04  <aklein>jwolfe: I do think there's work going on to show a more useful set of comments in the UI
19:36:22  <aklein>I see a bunch of open bugs related to this topic on https://bugs.chromium.org/p/gerrit/issues/
19:37:36  <jwolfe>aklein: cool. looks like a lot of good ideas there.
19:37:59  <jwolfe>one thing i just noticed though is there appears to be no keyboard shortcuts for navigating the comments section.
19:42:20  <aklein>interesting, that does seem like a big missing feature
19:42:39  * joyeequit (Read error: Connection reset by peer)
19:43:15  * joyeejoined
19:52:07  * seventhquit (Quit: ...)
19:53:19  * joyeequit (Read error: Connection reset by peer)
19:54:00  * joyeejoined
20:04:05  * joyeequit (Read error: Connection reset by peer)
20:04:30  * joyeejoined
20:14:42  * joyee_joined
20:14:43  * joyeequit (Read error: Connection reset by peer)
20:20:25  * joyee_quit (Read error: Connection reset by peer)
20:21:00  * joyeejoined
21:07:00  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
21:22:11  * joyeequit (Read error: Connection reset by peer)
21:22:21  * joyeejoined
21:31:01  * unixpicklejoined
21:33:11  * joyeequit (Read error: Connection reset by peer)
21:33:24  * joyeejoined
21:38:42  * joyeequit (Read error: Connection reset by peer)
21:38:48  * joyeejoined
21:50:31  * joyeequit (Read error: Connection reset by peer)
21:53:09  * joyeejoined
21:58:07  * xaxxonjoined
21:58:58  <xaxxon>I just updated to latest build of v8 and noticed the no-snapshot start up time got a LOT worse.. my old build (not more than a year old) would start up in ~3s without snapshots. The current build takes ~20s without snapshots
21:59:25  <xaxxon>I rebuilt with snapshots and that is still the expected speed, so it's not something naively dumb that I'm doing
22:00:29  <xaxxon>running without snapshots was much more convenient for me and the startup time was easily acceptable.. but at 20s it's painful to debug stuff, so I'm having to switch back to snapshots :(
22:03:01  * joyeequit (Read error: Connection reset by peer)
22:03:26  * joyeejoined
22:03:35  * bradleymeckquit (Quit: bradleymeck)
22:06:38  * joyeequit (Remote host closed the connection)
22:16:39  * joyeejoined
22:21:22  * joyeequit (Ping timeout: 264 seconds)
22:22:23  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
22:31:48  <jwolfe>i also experienced ~20s startup time with no snapshot, fwiw
22:33:33  <xaxxon>jwolfe, do you recall if this is a relatively new thing for you, as well?
22:34:17  <xaxxon>new meaning last 6-12 mo
22:36:50  <jwolfe>xaxxon: i only ever tried it recently.
22:36:56  <xaxxon>ok
22:38:11  <xaxxon>I had to update to get v8-inspector
22:41:52  * unixpicklejoined
22:49:01  * xaxxonquit (Ping timeout: 260 seconds)
22:49:57  * plutoniixquit (Quit: Leaving)
22:51:31  * RT|Chatzillajoined
23:02:09  * xaxxonjoined
23:07:21  <aklein>xaxxon: what did you find more convenient about the no-snapshot build?
23:07:46  <xaxxon>aklein, not having to have snapshots
23:08:22  <xaxxon>aklein, I mean.. that sounds flippant, right? but it's easier to not have them. The error messages when they're set up wrong (in any number of ways) are not useful (especially to beginners)
23:08:44  <xaxxon>if you have multiple builds, you have to make sure you have the right snapshots...
23:09:16  <xaxxon>it's just an optimization that wasn't at all necessary in my case
23:09:43  <aklein>I guess I'd ask, why was a 3s delay OK for you?
23:09:50  <xaxxon>so if the tradeoff was not having to manage these files and deal with the complexities involved in trade for.. I dunno, maybe 2s..
23:10:05  <aklein>got it, just a tradeoff
23:10:23  <xaxxon>because 3s was insignificant compared to the work being done afterwards
23:10:36  <xaxxon>but 20s isn't if you're just changing a small thing to see what happens
23:10:58  <xaxxon>the difference between waiting 1s for a program to start up and 3s isn't noticable to me.. it doesn't make me want to go browse the web
23:11:05  * scottmg_changed nick to scottmg
23:11:12  <xaxxon>but the difference between 3s and 20s is noticeable.
23:11:42  <xaxxon>aklein, do you know if/how/when a change was made that made the no-snapshot startup time significantly worse? or if I have somehow changed something else?
23:13:15  <aklein>xaxxon: I don't; I just know that the nosnapshot build is not a priority (and certainly not its speed), so it's not terribly surprising to me that it got slower. if I were to guess I'd blame it on the code stub assembler (we do a bunch of compilation work at startup now)
23:13:28  <xaxxon>aklein, if I were releasing an application that would otherwise start up instantly, I would have a release build that would ship with the snapshots, but that's not really the situation I'm in, so I worked with what worked best for me
23:14:02  <xaxxon>aklein, that's work that's been done in the last 6-12mo?
23:15:32  <xaxxon>whenever I was helping anyone getting started with v8, I always suggested they avoid snapshots, since that was often one of the problems they were having and they were always happy to not have to worry about it anymore. but now that's not a reasonable suggestion
23:16:03  <aklein>xaxxon: yes, it's relatively recent
23:16:07  * joyeejoined
23:16:22  <aklein>xaxxon: you could run a CPU profiler to test that guess
23:16:35  <xaxxon>... or just hit break at 10s
23:16:53  <xaxxon>low-frequency statistical analysis :)
23:18:32  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
23:20:00  <xaxxon>aklein, v8::internal::compiler::CodeGenerator::AssembleMove(...) and lots of other similar things?
23:20:21  <xaxxon>pipeline::genratecodeforcodestub...
23:20:25  <aklein>xaxxon: yup, that'd be us compiling CodeStubAssembler-based builtins
23:20:29  * joyeequit (Ping timeout: 240 seconds)
23:20:57  <xaxxon>so the point of the no-snapshot build is to build snapshots to use with the snapshot build, eh?
23:22:20  <xaxxon>it's fine. just gotta update a bunch of cmake configs to copy around these extra files
23:22:33  <xaxxon>I'll update my v8-users post with this info
23:25:37  <xaxxon>aklein, you have any information on what you have to do to with v8-inspector to reset the state to get it to deal with a new debugger? I have it working with the chrome debugger, but if I reload chrome, I have to restart the application otherwise it doesn't send the same messages (specifically something about "execution context started" or something similar
23:26:57  * unixpicklejoined
23:28:19  <aklein>xaxxon: no idea about that, sorry
23:28:34  <xaxxon>aklein, thanks for the info, though. at least I know it wasn't something on my end with the speed issue
23:52:22  * bradleymeckjoined