07:12:58  * rvaggtopic: there is no topic
07:20:50  * wolfeidauquit (Remote host closed the connection)
07:58:47  * ChrisPartridgequit
08:30:52  * dominictarrjoined
08:35:31  * no9joined
09:06:52  * ralphtheninjajoined
09:24:14  * st_lukequit (Remote host closed the connection)
09:25:21  * harethjoined
09:32:20  * dominictarrquit (Quit: dominictarr)
09:39:19  * no9quit (Ping timeout: 256 seconds)
09:47:53  * wolfeidaujoined
10:09:33  * levelbotjoined
10:09:33  <levelbot>[npm] abstract-leveldown@0.4.0 <http://npm.im/abstract-leveldown>: An abstract prototype matching the LevelDOWN API (@rvagg)
10:15:57  <levelbot>[npm] abstract-leveldown@0.4.0-1 <http://npm.im/abstract-leveldown>: An abstract prototype matching the LevelDOWN API (@rvagg)
10:17:03  <levelbot>[npm] leveldown@0.2.2 <http://npm.im/leveldown>: A Node.js LevelDB binding, primary backend for LevelUP (@rvagg)
10:20:27  <levelbot>[npm] abstract-leveldown@0.5.0 <http://npm.im/abstract-leveldown>: An abstract prototype matching the LevelDOWN API (@rvagg)
10:24:24  * wolfeidauquit (Remote host closed the connection)
10:28:23  * harethquit (Quit: hareth)
10:30:53  * harethjoined
10:46:58  <levelbot>[npm] abstract-leveldown@0.6.0 <http://npm.im/abstract-leveldown>: An abstract prototype matching the LevelDOWN API (@rvagg)
10:48:52  <rvagg>unpublished leveldown@0.2.2 fyi
10:56:36  <levelbot>[npm] leveldown@0.3.0 <http://npm.im/leveldown>: A Node.js LevelDB binding, primary backend for LevelUP (@rvagg)
10:59:08  <rvagg>thar we go
11:06:32  * mcollinajoined
11:07:41  <rvagg>bit more interesting in here mcollina
11:08:13  <mcollina>The other one was totally mute :P.
11:11:54  <mcollina>rvagg: I've seen the difference between a V8::Local and a V8::Persistent. Nice catch.
11:17:18  <rvagg>I need to look at juliangruber's chained batch code but that should make it in to an 0.9 release; but I'm hesitating because of detaching leveldown and the user-pain it's going to cause
11:20:22  <mcollina>detaching leveldown will cause user-pain, but it's for the better.
11:21:08  <mcollina>we need to state it very early in the README: we detached leveldown so you can run levelup in the browser, through browserify: here is the [link](...).
11:21:39  <rvagg>yeah, and it's not just browserify
11:21:45  <rvagg>it'll have to go at the top of the readme
11:29:01  <levelbot>[npm] abstract-leveldown@0.6.1 <http://npm.im/abstract-leveldown>: An abstract prototype matching the LevelDOWN API (@rvagg)
12:16:25  * levelbotquit (*.net *.split)
12:17:23  * levelbotjoined
12:18:01  <levelbot>[npm] abstract-leveldown@0.6.1 <http://npm.im/abstract-leveldown>: An abstract prototype matching the LevelDOWN API (@rvagg)
12:18:17  <rvagg>ugh, repetition again levelbot?
12:18:33  <levelbot>[npm] abstract-leveldown@0.6.1 <http://npm.im/abstract-leveldown>: An abstract prototype matching the LevelDOWN API (@rvagg)
12:22:54  * werlejoined
13:15:03  <levelbot>[npm] leveldown@0.3.1 <http://npm.im/leveldown>: A Node.js LevelDB binding, primary backend for LevelUP (@rvagg)
13:15:06  <levelbot>[npm] leveldown@0.3.1 <http://npm.im/leveldown>: A Node.js LevelDB binding, primary backend for LevelUP (@rvagg)
13:15:15  <levelbot>[npm] leveldown@0.3.1 <http://npm.im/leveldown>: A Node.js LevelDB binding, primary backend for LevelUP (@rvagg)
13:15:23  <levelbot>[npm] abstract-leveldown@0.7.0 <http://npm.im/abstract-leveldown>: An abstract prototype matching the LevelDOWN API (@rvagg)
13:15:25  <levelbot>[npm] abstract-leveldown@0.7.0 <http://npm.im/abstract-leveldown>: An abstract prototype matching the LevelDOWN API (@rvagg)
13:15:31  <levelbot>[npm] abstract-leveldown@0.7.0 <http://npm.im/abstract-leveldown>: An abstract prototype matching the LevelDOWN API (@rvagg)
13:16:17  <levelbot>[npm] memdown@0.2.0 <http://npm.im/memdown>: An drop-in replacement for LevelDOWN that works in memory only (@rvagg)
13:16:20  <levelbot>[npm] memdown@0.2.0 <http://npm.im/memdown>: An drop-in replacement for LevelDOWN that works in memory only (@rvagg)
13:16:26  <levelbot>[npm] memdown@0.2.0 <http://npm.im/memdown>: An drop-in replacement for LevelDOWN that works in memory only (@rvagg)
13:16:29  <rvagg>hmm
13:33:53  <rvagg>you need to keep chipping away at @3rdeden juliangruber
13:34:34  <juliangruber>rvagg: what does to chip away mean?
13:35:04  <rvagg>ah, keep on working on him
13:35:10  <juliangruber>yes!
13:35:19  * no9joined
13:35:20  <juliangruber>it would be cool to get him on the boat
13:35:34  <rvagg>he's been vocal about the "one process limit", he needs convincing; a smart guy, respected member of the community, would be a good one to bring around
13:35:58  <juliangruber>we already have quite a few respected members of the community on board :)
13:36:08  * werlequit (Quit: Leaving.)
13:36:12  <rvagg>aye
13:36:20  <juliangruber>let's see what he says about multilevel
13:36:55  <rvagg>I made contact with the basho leveldb guy today, he has a nice leveldb benchmark suite that I've asked to 'borrow'
13:37:03  <juliangruber>sweet
13:37:15  <juliangruber>cian also was interested in porting bencharks
13:37:20  <juliangruber>from the official leveldb repo
13:37:29  <rvagg>cause they care a lot more than most about long-running, high-throughput server-side stuff than most leveldb users
13:37:44  <juliangruber>cool
13:38:09  <juliangruber>but we need more than thet
13:38:15  <juliangruber>we need stream benchmarks too
13:38:43  <juliangruber>/thet/that
13:38:49  <rvagg>their fork is pretty radical compared to the main leveldb release tho, it's a tricky one but if we have some good benchmarks and understand the tradeoffs better then we ought to be able to recommend to people the appropriate 'backend' for levelup
13:39:09  <juliangruber>oh, what did they change?
13:39:15  <rvagg>a whole bunch of things
13:39:42  <juliangruber>maybe we can port over stuff that makes sense?
13:39:43  <rvagg>he's sus about the default bloom filter for example, replaced that, they have multiple threads doing compactions at the different levels too
13:40:09  <rvagg>well, I already have a leveldown (in a branch somewhere) that uses their leveldb, I did some superficial benchmarks a while back that didn't show any difference
13:40:26  <juliangruber>mhm
13:40:29  <juliangruber>but maybe on long running ops
13:40:31  <rvagg>but that's cause they've targeted a situation that our lame benchmarks don't touch on
13:40:42  <rvagg>yeah, high throughput, heavy writes mainly
13:40:59  <rvagg>multiple threads for compactions is nice
13:41:31  <rvagg>they've also messed a bit with level 1 & 2 I think, allowing overlapping ranges in level 2 which isn't standard, I can't remember if it's standard in level 1 either
13:41:36  <juliangruber>we could put together some money and to week-long stress tests on vms
13:41:48  <juliangruber>/to/do/
13:41:54  <juliangruber>vms=in the cloud
13:42:02  <rvagg>anyway, I'm totally leveldb'd out now, been hacking on it for the past 4 hours or so
13:42:04  <rvagg>and it's bed time
13:42:06  <rvagg>so ta ta!
13:42:07  <juliangruber>shit, my brain's broken today
13:42:13  <juliangruber>oh lala
13:42:15  <juliangruber>gn8 sir
13:42:30  <juliangruber>and see ya tomorrow
13:51:21  <no9>rvagg nighty night
13:53:26  <no9>Just so y'all know we are starting a leveldb production project this week :
13:58:31  * cianomaidinjoined
14:04:07  * mcollinaquit (Ping timeout: 264 seconds)
14:16:33  * mcollinajoined
14:17:46  <cianomaidin>no9: have you told peeps about our GSD production project
14:23:57  <no9>cianomaidin just mentioned it before you logged in
14:28:42  <cianomaidin>kewl
14:31:15  * ralphthe1injajoined
14:35:58  * harethquit (*.net *.split)
14:35:58  * ralphtheninjaquit (*.net *.split)
14:35:59  * timoxleyquit (*.net *.split)
14:50:27  * cianomaidinquit (Quit: cianomaidin)
15:05:29  * no9quit (Ping timeout: 245 seconds)
15:05:40  * ralphthe1injachanged nick to ralphtheninja
15:16:04  * slurp1joined
15:16:04  * rvaggtopic: there is no topic
15:23:31  * slurpquit (*.net *.split)
15:23:33  * hij1nxquit (*.net *.split)
15:24:07  * Pwnnajoined
15:25:21  * cianomaidinjoined
15:26:13  * timmakjoined
15:26:20  <timmak>hi using sublevel and levelup, the sublevel has method object attached to it is this used for anything?
15:32:34  * hij1nxjoined
15:43:57  <ralphtheninja>timmak: I suggest you ask dominic tarr about that
15:44:55  <timmak>thanks
15:45:06  <ralphtheninja>np :)
15:49:12  * mreviljoined
15:56:49  * werlejoined
16:35:03  * cianomaidinquit (Quit: cianomaidin)
16:40:01  * cianomaidinjoined
17:04:35  * Pwnnaquit (Read error: Connection reset by peer)
17:04:57  * Pwnnajoined
17:07:16  * mcollinaquit (Ping timeout: 256 seconds)
17:21:14  * cianomaidinquit (Quit: cianomaidin)
17:23:08  * dominictarrjoined
17:26:45  <levelbot>[npm] magpie@0.0.2 <http://npm.im/magpie>: Simple persistence for rapid prototyping. Powered by levelup. (@capelio)
17:26:49  <levelbot>[npm] magpie@0.0.2 <http://npm.im/magpie>: Simple persistence for rapid prototyping. Powered by levelup. (@capelio)
17:26:56  <levelbot>[npm] magpie@0.0.2 <http://npm.im/magpie>: Simple persistence for rapid prototyping. Powered by levelup. (@capelio)
17:31:47  * dominictarrquit (Quit: dominictarr)
18:05:09  * werlequit (Read error: Operation timed out)
18:08:10  * werlejoined
18:15:13  <levelbot>[npm] magpie@0.0.3 <http://npm.im/magpie>: Simple persistence for rapid prototyping. Powered by levelup. (@capelio)
18:15:18  <levelbot>[npm] magpie@0.0.3 <http://npm.im/magpie>: Simple persistence for rapid prototyping. Powered by levelup. (@capelio)
18:15:24  <levelbot>[npm] magpie@0.0.3 <http://npm.im/magpie>: Simple persistence for rapid prototyping. Powered by levelup. (@capelio)
19:03:17  <levelbot>[npm] level-model@0.0.1 <http://npm.im/level-model>: level-model (@werle)
19:03:21  <levelbot>[npm] level-model@0.0.1 <http://npm.im/level-model>: level-model (@werle)
19:03:25  <werle>just published https://github.com/jwerle/level-model
19:03:28  <levelbot>[npm] level-model@0.0.1 <http://npm.im/level-model>: level-model (@werle)
19:13:50  <werle>@chapel I decided to abstract the collection stuff into its own module and left level-model alone
19:18:53  <chapel>werle: did you see unid?
19:19:18  <werle>@chapel I did and I'm going to use it with level-collection
19:19:43  <chapel>cool, feel free to post any issues/pr's if you find anything
19:19:54  <chapel>or see any room for improvement
19:20:07  <werle>@chapel do you think it would be useful to use as the key in which models are saved with?
19:20:15  <chapel>when I did some simple benchmarks, I was getting 730k keys a second
19:20:40  <chapel>well how I am using it is as the primary key for model documents
19:20:47  <chapel>similar to mongo
19:22:10  <werle>oh wow
19:22:13  <werle>I want to see that
19:25:00  <chapel>see what?
19:36:57  * ramitosjoined
19:53:38  <werle>@chapel what you've been using unid for
19:53:48  <chapel>oh lol
19:58:56  <chapel>werle: Im refactoring the logic, realizing it makes sense to have a lower level implementation similar to a base mongo driver
19:59:07  <chapel>and then anything on top of that could be like mongoose
20:00:14  <werle>@chapel nice
20:00:39  <chapel>been busy though, I am moving down to the bay area saturday
20:00:46  <chapel>so not much time for coding last few days
20:01:27  * Pwnnaquit (Ping timeout: 260 seconds)
20:10:02  <werle>Moving is a drag
20:10:06  <werle>I undersand that
20:15:00  * Pwnnajoined
20:36:39  * Raynos_joined
20:51:45  * timmakquit (Ping timeout: 248 seconds)
21:12:39  * timmakjoined
21:17:19  * cianomaidinjoined
21:22:48  * cianomaidinquit (Quit: cianomaidin)
21:45:59  * cianomaidinjoined
21:47:06  * cianomaidinquit (Client Quit)
22:29:04  * timmakquit (Quit: Lost terminal)
22:34:42  * cianomaidinjoined
22:47:14  * st_lukejoined
22:50:21  * wolfeidaujoined
22:55:25  * mrevilquit (Remote host closed the connection)
23:09:14  * st_lukequit (Remote host closed the connection)
23:10:28  * no9joined
23:10:40  * ralphtheninjaquit (Read error: Operation timed out)
23:19:23  * cianomaidinquit (Quit: cianomaidin)
23:27:25  * werlequit (Quit: Leaving.)
23:27:31  * wolfeidauquit (Remote host closed the connection)
23:28:07  * wolfeidaujoined
23:35:50  * no9quit (Quit: Leaving)
23:50:15  * mbalhoquit (Ping timeout: 240 seconds)