00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:10  * ircretaryjoined
00:56:35  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
01:08:50  * hzquit
01:16:56  <ryah>mmalecki: hi :)
01:30:45  * wavdedjoined
01:32:40  <tjfontaine>bnoordhuis:
01:32:41  <tjfontaine>stap -I . -e 'probe node_net_server_connection { println(probestr); }'
01:32:41  <tjfontaine>net__server__connection(remote=127.0.0.1, port=49564, fd=14)
01:32:42  <tjfontaine>net__server__connection(remote=127.0.0.1, port=49565, fd=15)
01:32:51  <tjfontaine>pretty
01:34:12  <bnoordhuis>nice
01:34:29  <tjfontaine>using only node_provider.d and a tapset file
01:34:39  <tjfontaine>so we won't have to maintain two separate things
01:34:44  <bnoordhuis>nice work
01:35:39  <tjfontaine>it's a start anyway, I hope it makes people actually use it
01:41:04  * howdynihaojoined
01:43:00  <bnoordhuis>hm, DST. i should get to bed
01:43:03  <bnoordhuis>sleep tight
01:43:22  <tjfontaine>enjoy!
01:48:00  * bnoordhuisquit (Ping timeout: 256 seconds)
02:05:15  <wolfeida_>tjfontaine: what OS are you using for stap?
02:06:07  <tjfontaine>wolfeida_: ubuntu
02:06:46  <wolfeida_>tjfontaine: Just apt-get install stap? I did most of my stap stuff on centos as ubuntu was a mess
02:07:21  <tjfontaine>wolfeida_: I'm testing on 13.04, it's been mostly hasslefree
02:07:45  <howdynihao>whats the easiest way to run a comparison benchmark? like the one in the 0.10.0 blog post
02:07:53  <howdynihao>between master and my branch
02:08:42  <wolfeida_>tjfontaine: Yeah i read that 12.10 they had done some work on making it easier, should give it a try as dtrace in linux looks like a no show
02:09:12  <tjfontaine>wolfeida_: it's there but I haven't really tried it
02:09:25  <tjfontaine>howdynihao: I believe it's benchmark/compare.js
02:10:54  <wolfeida_>tjfontaine: Did you see the presentation by brendan gregg which provided a rundown on linux perf tools? I think he mentioned that dtrace linux stuff was still pretty unstable
02:12:12  <wolfeida_>Either way I would like to try stap again, used it for some ext3 fs debugging which was mildly successful
02:12:15  <tjfontaine>I have no doubt it is, I'll ask him monday at work :P
02:12:22  <wolfeida_>tjfontaine: lol
02:13:53  <wolfeida_>tjfontaine: Tell him his presentation on linux perf tools rocked :)
02:14:10  <tjfontaine>hehe I will do that
02:15:04  <wolfeida_>tjfontaine: This is the one http://www.slideshare.net/brendangregg/linux-performance-analysis-and-tools currently use it as the one stop shop for WTF linux :)
02:16:31  <tjfontaine>I know he was mentioning that he was getting a lot traction off those slides
02:18:15  <wolfeida_>tjfontaine: He did an amazing job, it would almost be worth turning into a poster for those new to systems perf / fault analysis
02:23:15  <tjfontaine>wolfeida_: I'm hoping to get smarter by just listening to him at work :)
02:24:39  <tjfontaine>I am also hoping to get see some of his talks in person
02:26:42  <wolfeida_>tjfontaine: haha yeah i envy you, brendan and bryan cantrill are damn smart engineers with a ton of experience
02:27:24  * brsonjoined
02:28:41  <tjfontaine>wolfeida_: honestly, every engineer at joyent is like that, I am incredibly lucky to have the job
02:31:55  <wolfeida_>tjfontaine: yeah for sure, I have a lot of respect for them having used solaris and smartos pity more people aren't using it :)
02:33:29  <howdynihao>https://github.com/joyent/node/blob/master/lib/events.js#L114
02:33:42  <howdynihao>why this line?
02:34:09  <howdynihao>i want to remove it in my pull request, but im afraid it seems so obviously pointless, thats why im afraid haha why its there
02:34:49  <howdynihao>that maybe it just has a point? but i dont know!
02:37:39  <howdynihao>it's probably hanging around from legacy code or something
02:38:10  <howdynihao>so i need a faster computer... trying to compile, benchmark, run tests... everything takes a long long time
02:45:56  * howdynihaoquit (Remote host closed the connection)
02:48:49  * xaqjoined
02:49:31  * benoitcquit (Excess Flood)
02:49:41  * howdynihaojoined
02:52:08  * benoitcjoined
02:53:35  * bnoordhuisjoined
02:54:02  <tjfontaine>bnoordhuis: you shouldn't irc in your sleep, it's bad for your health
02:54:43  <howdynihao>did someone mention something about my question? i disconnected for a sec there
02:55:13  <tjfontaine>howdynihao: no, see also http://logs.nodejs.org
02:56:55  <howdynihao>is there a benchmark/compare for tests? that is something easier than noting which tests fail currently on master, then making its not any new failed tests on my branch?
02:57:07  <howdynihao>making sure*
02:58:05  * bnoordhuisquit (Ping timeout: 255 seconds)
03:03:27  * xaq_joined
03:06:19  <tjfontaine>howdynihao: not as far as I know, but you could tweak it so that compare only runs a subset, or a single test
03:06:22  <tjfontaine>*bench
03:07:05  * xaqquit (Ping timeout: 255 seconds)
03:13:54  <howdynihao>well you know i accidentally ran the the compare benchmark against the same two binaries haha
03:14:10  <howdynihao>but surprisingly one benchmark actually achieved 20% more, even though its the same
03:14:58  <howdynihao>so i guess i should probably run the full suite of benchmarks just in case there's some weird false positives in a test
03:15:14  <tjfontaine>howdynihao: when you're doing taht stuff make sure you're doing absolutely nothing else on your computer
03:15:48  <howdynihao>well i think say if you compare node1 vs node2, node2 is at the disadvantage
03:15:54  <howdynihao>because it runs after
03:16:26  <howdynihao>the system is probably bogged down from running node1
03:16:38  <howdynihao>probably should have some sort of delay for the system load to go down before starting node2 ?
03:17:28  <howdynihao>i say that because across the board node2 was the slowest even though it was the same binary
03:17:30  <howdynihao>which is weird
03:18:11  <tjfontaine>howdynihao: presuming they run long enough windup/cooldown time shouldn't matter
03:20:18  * wavdedquit (Quit: Hasta la pasta)
03:26:16  * benoitcquit (Excess Flood)
03:32:38  * benoitcjoined
03:43:12  * brsonquit (Quit: leaving)
03:44:51  * AvianFluquit
03:51:20  * howdynihaoquit (Remote host closed the connection)
04:06:05  * kazuponjoined
04:15:36  * xaq_quit (Remote host closed the connection)
04:17:25  * brsonjoined
04:21:12  * howdynihaojoined
04:30:45  <tjfontaine>wolfeida_: https://github.com/joyent/node/pull/5182
04:39:12  * Raynosquit (Remote host closed the connection)
04:39:13  * dscapequit (Remote host closed the connection)
04:40:57  * howdynihaoquit (Remote host closed the connection)
05:00:07  <wolfeida_>tjfontaine: Nice will give it a try
05:09:13  * defunctzombiechanged nick to defunctzombie_zz
05:58:46  * kazuponquit (Remote host closed the connection)
06:02:43  * kazuponjoined
06:27:40  * mikealjoined
06:29:11  * mikealquit (Client Quit)
07:00:53  * stagasjoined
07:28:15  * benoitcquit (Excess Flood)
07:36:13  * kazuponquit (Remote host closed the connection)
07:38:45  * benoitcjoined
08:06:34  * kazuponjoined
08:07:10  * hzjoined
08:15:12  * kazuponquit (Ping timeout: 272 seconds)
08:30:53  * rendarjoined
08:40:48  * `3rdEdenjoined
08:49:17  * benoitcquit (Excess Flood)
08:55:44  * benoitcjoined
09:05:32  * `3rdEdenquit (Remote host closed the connection)
09:09:35  * brsonquit (Ping timeout: 260 seconds)
09:11:49  * kazuponjoined
09:16:35  * kazuponquit (Ping timeout: 260 seconds)
09:35:16  * kazuponjoined
09:35:39  * kazuponquit (Read error: Connection reset by peer)
09:35:56  * kazuponjoined
10:15:39  * dominictarrjoined
10:23:24  * paddybyersjoined
10:43:30  * dominictarrquit (Quit: dominictarr)
10:45:29  * paddybyersquit (Ping timeout: 246 seconds)
10:49:17  <rendar>can i disable *all* i/o completions in libuv? if so, how it works? are there flags for each i/o completion operation, and if the flag is not set the completion callback is not called?
10:55:56  * dominictarrjoined
11:03:10  * dominictarrquit (Quit: dominictarr)
11:15:15  * stagasquit (Quit: Bye)
11:42:12  * dominictarrjoined
11:43:13  * kazuponquit (Remote host closed the connection)
11:43:39  * kazuponjoined
11:48:38  * kazuponquit (Ping timeout: 272 seconds)
12:37:39  * dscapejoined
12:45:47  * dominictarrquit (Ping timeout: 255 seconds)
12:57:57  * Raynosjoined
13:42:21  * c4milojoined
14:24:36  * c4miloquit (Remote host closed the connection)
14:30:14  * stagasjoined
14:52:41  * c4milojoined
15:06:55  * kazuponjoined
15:09:24  * dominictarrjoined
15:16:38  * dominictarrquit (Ping timeout: 256 seconds)
15:18:27  * dominictarrjoined
15:24:05  * kazuponquit (Remote host closed the connection)
15:27:49  * dominictarrquit (Quit: dominictarr)
15:31:58  * defunctzombie_zzchanged nick to defunctzombie
15:40:05  * c4miloquit (Remote host closed the connection)
16:02:58  * xaqjoined
16:11:37  * c4milojoined
16:34:32  * kazuponjoined
16:35:40  * c4miloquit (Remote host closed the connection)
16:36:13  * c4milojoined
16:38:15  * kazupon_joined
16:38:53  * kazuponquit (Ping timeout: 240 seconds)
16:40:30  * c4miloquit (Ping timeout: 256 seconds)
17:02:52  * kazupon_quit (Remote host closed the connection)
17:07:26  * kazuponjoined
17:11:28  <indutny>hey people
17:15:11  * paddybyersjoined
17:27:00  * paddybyersquit (Ping timeout: 240 seconds)
17:31:33  * bnoordhuisjoined
17:33:28  <bnoordhuis>creationix: was it you that created the 'gypified' account on github?
17:33:46  <indutny>heh
17:33:50  <indutny>either tim or bert
17:36:07  <indutny>bnoordhuis: what would you think about system-level scripting language
17:36:14  <indutny>with C compatible syntax
17:36:22  <indutny>and both managed and unmanaged allocations
17:37:04  <indutny>compatible with C in only one direction
17:37:11  <indutny>C code will work in that language
17:37:18  <bnoordhuis>indutny: like rust or ats, you mean?
17:37:26  <indutny>not like rust
17:37:27  <bnoordhuis>or more like varnish's vcl?
17:37:46  <indutny>ATS
17:37:48  <indutny>interesting
17:38:14  <indutny>no
17:38:33  <indutny>meh, only rust looks mature
17:38:38  <indutny>but its very different
17:38:49  <indutny>from C
17:39:22  <bnoordhuis>yes
17:39:36  <bnoordhuis>it's a functional language disguising itself as a system language
17:39:41  <indutny>yeh
17:39:46  <indutny>I know, its quite good, actually
17:39:50  <bnoordhuis>i kind of like it though
17:39:54  <indutny>considering its robustness
17:40:04  <indutny>hm... may be I should work on it instead
17:46:57  <tjfontaine>bnoordhuis: did you get a chance to try out that tapset helper?
18:03:27  <MI6>joyent/libuv: Ben Noordhuis v0.10 * ec24bfa : include: update uv_backend_fd() documentation uv_run_once() is no more, - http://git.io/TKW1qw
18:03:35  <bnoordhuis>tjfontaine: not yet but it looks okay to me
18:05:47  <MI6>libuv-v0.10: #25 UNSTABLE windows (7/187) linux (3/186) osx (1/186) smartos (4/186) http://jenkins.nodejs.org/job/libuv-v0.10/25/
18:31:26  * c4milojoined
18:38:56  * kazuponquit (Remote host closed the connection)
18:41:18  * piscisaureus_joined
18:41:49  * xaqquit (Remote host closed the connection)
18:42:15  * benoitcquit (Excess Flood)
18:42:37  * xaqjoined
18:45:22  * benoitcjoined
18:46:56  * xaqquit (Ping timeout: 256 seconds)
19:09:19  * kazuponjoined
19:09:27  <txdv>!now No Swear
19:09:30  <txdv>o
19:14:10  * AvianFlujoined
19:17:30  * kazuponquit (Ping timeout: 240 seconds)
19:17:58  <indutny>txdv: ?
19:18:11  <txdv>wrong channel
19:19:34  * stagasquit (Ping timeout: 245 seconds)
19:33:21  * xaqjoined
19:33:32  * piscisaureus_quit (Quit: ~ Trillian Astra - www.trillian.im ~)
19:39:29  * paddybyersjoined
19:43:24  * c4miloquit (Remote host closed the connection)
19:43:59  * c4milojoined
19:46:27  * indexzerojoined
19:48:38  * c4miloquit (Ping timeout: 256 seconds)
20:14:33  * kazuponjoined
20:17:29  * benoitcquit (Excess Flood)
20:18:57  * kazuponquit (Ping timeout: 252 seconds)
20:19:22  * benoitcjoined
20:26:38  * defunctzombiechanged nick to defunctzombie_zz
20:35:29  * defunctzombie_zzchanged nick to defunctzombie
20:43:37  * hzquit
21:00:00  * defunctzombiechanged nick to defunctzombie_zz
21:01:39  * loladirojoined
21:08:02  * brsonjoined
21:09:19  * xaqquit (Remote host closed the connection)
21:11:39  * xaqjoined
21:12:19  * jez0990quit (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)
21:13:13  * xaqquit (Remote host closed the connection)
21:13:41  * jez0990joined
21:15:10  * kazuponjoined
21:21:23  * loladiroquit (Quit: loladiro)
21:21:29  * kazuponquit (Ping timeout: 255 seconds)
21:23:23  * rendarquit
21:24:01  * benoitcquit (Excess Flood)
21:28:21  * benoitcjoined
21:39:06  * Raynosquit (Remote host closed the connection)
21:39:07  * dscapequit (Write error: Broken pipe)
21:39:33  * xaqjoined
21:39:55  * loladirojoined
21:55:24  * paddybyersquit (Ping timeout: 245 seconds)
21:56:40  * defunctzombie_zzchanged nick to defunctzombie
21:57:15  * benoitcquit (Excess Flood)
22:00:52  * benoitcjoined
22:08:37  * loladiroquit (Quit: loladiro)
22:11:52  * trevnorrisjoined
22:14:15  <trevnorris>bnoordhuis: "Buffer::New(Handle<String> string)" isn't used or documented. can it be removed?
22:15:18  <bnoordhuis>trevnorris: is it declared in node_buffer.h?
22:15:50  <trevnorris>bnoordhuis: yeah. though the comment above it doesn't make any sense: "C++ API for constructing fast buffer"
22:17:27  <bnoordhuis>node_buffer.h is public so no, it can't be flat out removed
22:17:36  <trevnorris>deprecated then?
22:17:41  <bnoordhuis>well, maybe
22:17:43  <bnoordhuis>why?
22:17:48  * kazuponjoined
22:18:14  <trevnorris>it isn't used, and it shouldn't be used. the code in there sucks. ;-)
22:18:51  <trevnorris>it gets the Buffer js function (uncached) every time then calls to it w/ a string. so that Buffer can call .write
22:19:04  <trevnorris>which then calls back to cc to one of the *Write methods.
22:19:11  <bnoordhuis>yes. works as advertised, doesn't it?
22:19:15  <trevnorris>lol
22:21:29  * brsonquit (Ping timeout: 240 seconds)
22:22:23  <trevnorris>ok. just makes me hurt a little inside seeing it like that.
22:22:26  <wolfeida_>tjfontaine: Got stap installed and kinda working on 12.04.1 do I need to enable dtrace via ./configure to test out that patch
22:22:34  * kazuponquit (Ping timeout: 258 seconds)
22:23:21  <bnoordhuis>wolfeida_: ./configure --with-dtrace
22:23:32  <wolfeida_>bnoordhuis: Thanks
22:23:48  <trevnorris>what about global-izing the encoding enum (from ByteLength), and expanding that ::New to call directly to the utf8 write as the default.
22:23:55  <trevnorris>(since that's what's happening anyways)
22:25:10  <bnoordhuis>trevnorris: *shrug*
22:25:37  <bnoordhuis>premature optimization, root of all evil, etc.
22:25:56  <trevnorris>heh
22:26:41  <trevnorris>oh, was it you or someone else that mentioned the new v8 WriteOneByte is pretty much treating the data as binary?
22:27:16  * howdynihaojoined
22:28:09  <bnoordhuis>don't think it was me but it sounds plausible it works like that
22:28:21  <howdynihao>ugh
22:28:21  <trevnorris>ah yeah. think it was pisc
22:28:28  <trevnorris>just ask because ::BinaryWrite calls to DecodeWrite which has several comments about needing to be improved.
22:29:07  <trevnorris>anyways. enough of that for the day. thanks. =)
22:29:15  <howdynihao>so i wanted to start cleaning up eventemitter some, to reduce some of the redundancy, unfortunately, performance is a mix bag
22:29:30  <howdynihao>im guessing thats 100% no to any code approval?
22:29:56  <trevnorris>howdynihao: give me some examples of changes you'd like to do
22:30:09  <bnoordhuis>trevnorris: right. it might help in DecodeWrite
22:30:19  <howdynihao>https://github.com/lovebear/node/commit/556b00e693f974d63d5ed0a869d17992c2b52964 this is what im starting with
22:30:19  <bnoordhuis>there's still tons of people that use binary encoding
22:30:34  <trevnorris>bnoordhuis: cool. i'll look into it. thanks.
22:30:35  <bnoordhuis>and the current algorithm (if you can call it that) is less than optimal
22:30:36  <howdynihao>but yea so the performance takes a hit for single objects, but improvement for an array
22:30:40  <howdynihao>single function*
22:30:54  <howdynihao>mainly my objective was to reduce the redundancy
22:30:59  <bnoordhuis>howdynihao: was it you who asked about that slice call in there?
22:31:00  <trevnorris>howdynihao: problem is single function callbacks are used 99.9% of the time.
22:31:20  <howdynihao>trevnorris: yea... :(
22:31:32  <howdynihao>bnoordhius: yea it was, i realize its needed
22:32:39  <trevnorris>howdynihao: i also tried to make the call more generic by always wrapping the function in an array. crazy how much performance that killed.
22:33:33  <howdynihao>yea, i mean if this can't be cleaned up with some acceptable performance hit on the single object events
22:33:49  <howdynihao>then i guess no chance to have a simple catch all event :x
22:34:36  <howdynihao>which sucks, because i think a catch all event opens up a lot more possibilities for users
22:35:01  <bnoordhuis>that's something that's been discussed at length in the past
22:35:22  <indutny>hey people
22:35:28  <bnoordhuis>not just by core team members btw
22:35:29  <indutny>what do you think about http://blog.indutny.com/
22:35:35  <indutny>does it looks better now?
22:35:53  <trevnorris>bnoordhuis: lol. seems i already made that change to DecodeWrite same time i changed it for AsiiWrite.
22:36:02  <trevnorris>guess only other improvement would be to call it directly from DecodeWrite. but that's minor at best.
22:36:14  <howdynihao>bnoordhius: i was able to find a few, im guessing the ultimate reason it was rejected was because it'll add complexity to the code?
22:36:18  <trevnorris>erm. directly from BinaryWrite
22:36:33  <bnoordhuis>howdynihao: that and the fact that you'll never be able to please everyone
22:37:00  <bnoordhuis>that said, the eventemitter module is frozen. we won't be adding new features to it
22:37:17  <trevnorris>indutny: looks good. type face is 80% of a site, and you made all the right choices.
22:37:29  <indutny>whoa! finally :)
22:37:34  <indutny>I just decided to make it readable
22:37:35  <bnoordhuis>there's user land modules like eventemitter2 that build on top of it and add things like wildcard events
22:37:46  <indutny>trevnorris: thanks
22:37:58  <bnoordhuis>indutny: "bears"?
22:38:05  <indutny>bnoordhuis: vodka?
22:38:05  <bnoordhuis>you know that's gay slang, right?
22:38:09  <indutny>bnoordhuis: nope
22:38:11  * xaqquit (Remote host closed the connection)
22:38:26  <bnoordhuis>well, now you do. google it if you're curious
22:38:41  <howdynihao>bnoordhius: oh yea, but i figured if something what i linked above went through, then a catch all event would be 1 if statement line in emit() and then like 3 lines in the addListener, and 1,2 in removeListener
22:38:59  <indutny>bnoordhuis: oh... well... fuck it :)
22:39:04  <indutny>bnoordhuis: I don't care about it
22:39:06  <howdynihao>basically maybe increasing the chances of it going through ;)
22:39:09  <indutny>not that much
22:39:31  <bnoordhuis>howdynihao: not to kill all hope but the chances are effectively zero
22:39:42  <howdynihao>haha
22:41:15  <bnoordhuis>indutny: what does the +65 bit mean?
22:41:23  <indutny>social metric
22:41:27  <indutny>i.e. - "likes"
22:41:42  <bnoordhuis>ah
22:42:36  <txdv>nice font size
22:44:36  <howdynihao>bnoordhius: would a benchmark for specifically eventemitter emit be useful?
22:45:13  <bnoordhuis>howdynihao: sure
22:45:27  <bnoordhuis>i thought we already had a few but seems not
22:50:48  <trevnorris>indutny: np
22:55:09  * trevnorrisquit (Ping timeout: 258 seconds)
22:56:06  * luigyjoined
22:59:16  * loladirojoined
23:02:14  * brsonjoined
23:02:15  <tjfontaine>wolfeida_: did you end up getting it to work then?
23:03:10  <wolfeida_>tjfontaine: Reinstalling latest ubuntu as 12.04 with systemtap is completely screwed
23:03:30  <tjfontaine>ya I've heard similar things, 13.04 worked with little coaxing
23:04:16  <wolfeida_>tjfontaine: Yeah same issues aas when i last tried it, errors compiling the stap things with odd missing this and that errors
23:04:39  <tjfontaine>wolfeida_: frustrating.
23:04:40  <wolfeida_>tjfontaine: Got you code out and built, was i suppose enable dtrace in build as that didn't work
23:05:08  <tjfontaine>ya, it's an explicit enabling
23:05:47  <wolfeida_>tjfontaine: So what is the ./configure flag or was there somethihng else to tweak?
23:06:12  <tjfontaine>./configure --with-dtrace
23:06:23  <wolfeida_>tjfontaine: When i tried with --with-dtrace tried to locate the dtrace executable
23:06:36  <tjfontaine>ya, systemtap ships a dtrace executable
23:06:36  <wolfeida_>tjfontaine: During the build process
23:06:44  <wolfeida_>ok..
23:06:50  <tjfontaine>you need systemtap-sdt or similar named
23:06:56  <wolfeida_>AHA
23:07:04  <tjfontaine>systemtap-sdt-dev
23:07:07  <wolfeida_>god i hate system tape
23:07:10  <wolfeida_>tap even
23:07:45  <tjfontaine>once you get past this part it's ok, but I thought the d script syntax was painful, systemtap's is a bit over the top
23:07:59  <tjfontaine>at times, having the tapsets make it livable
23:08:26  <tjfontaine>also, the compile process for stap is depressingly slow (at least in my vm) compared to how fast dtrace enables probes
23:08:59  <wolfeida_>tjfontaine: Well i am going to try with 12.10 which i am installing now, will gist up how i get it working so we can fill in the gaps :)
23:09:21  <tjfontaine>on the plus side though, systemtap can reuse the same probes we define for dtrace, so supporting it requires little overhead from us
23:09:34  <tjfontaine>wolfeida_: I have hopes that 12.10 will work without much effort
23:10:34  <wolfeida_>tjfontaine: Yeah i love the idea of sharing those probes and stap overall is suppose to be quite good, albeit a bit unstable at times
23:14:15  <tjfontaine>being able to reuse the probe definitions among dtrace/systemtap/etw is quite a boon, though etw still needs a few more steps to make the probes useful, if we start adding more probe points it might be beneficial for us to do some scripting to define them, though I can't see much need beyond what we have
23:15:04  <tjfontaine>I have some probepoints for buffer allocs that I was playign with for trevnorris
23:15:09  * benoitcquit (Excess Flood)
23:15:52  * defunctzombiechanged nick to defunctzombie_zz
23:18:25  * kazuponjoined
23:18:40  * howdynihaoquit (Remote host closed the connection)
23:19:17  <wolfeida_>tjfontaine: Yeah telemetry is an awesome tool, I will keep you updated on how i go either way :)
23:19:20  * dscapejoined
23:22:09  <tjfontaine>:)
23:22:59  * kazuponquit (Ping timeout: 255 seconds)
23:24:54  * benoitcjoined
23:27:07  * indexzeroquit (Quit: indexzero)
23:50:04  * Raynosjoined
23:51:21  * benoitcquit (Excess Flood)
23:51:28  * benoitcjoined
23:54:43  * mikealjoined