00:03:26  * lithiumjakequit (Ping timeout: 276 seconds)
00:06:25  * thlorenzjoined
00:07:49  <levelbot>[npm] [email protected] <http://npm.im/levelup-cache>: Use LevelUP to cache remote data (@tehshrike)
00:09:54  * mcavagejoined
00:14:02  * ednapiranhajoined
00:18:58  * brianloveswordsquit (Quit: Computer has gone to sleep.)
00:21:55  * brianloveswordsjoined
00:26:20  * thlorenzquit (Remote host closed the connection)
00:27:56  * thlorenzjoined
00:29:25  * thlorenzquit (Remote host closed the connection)
00:29:40  * thlorenzjoined
00:31:48  * mcavagequit (Remote host closed the connection)
00:35:37  * ashihjoined
00:59:41  * ashihquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
01:04:21  * ashihjoined
01:04:28  * ashihquit (Client Quit)
01:11:28  * lithiumjakejoined
01:27:57  * ednapiranhaquit (Remote host closed the connection)
01:31:48  * lithiumjakequit (Ping timeout: 252 seconds)
01:33:48  * lithiumjakejoined
01:47:25  * prettyrobotsjoined
02:01:06  * theRealGentjoined
02:01:49  <theRealGent>hey all. Does leveldb usually take a while to compile? I’m installing through pip on os x, got a bunch of warnings, and it seems ot be compiling. I’m seeing the xcode xcrun process eating all my CPU % for like 20 minutes now...
02:02:09  <rescrv>theRealGent: that's unusually long
02:03:14  <theRealGent>constantly on snappy.o
02:03:16  <rescrv>I recompiled in the time between these messages just now on Linux. OS X is not noticably longer.
02:03:59  <theRealGent>compiling from source tarball or pip?
02:05:42  * ednapiranhajoined
02:09:49  <rescrv>source tarball
02:09:52  <rescrv>it's the same code
02:13:11  * lithiumjakequit (Ping timeout: 252 seconds)
02:13:54  * lithiumjakejoined
02:18:56  <theRealGent>here’s some of the output http://pastie.org/private/blhrictkvc5qjnilokuuww
02:19:04  <theRealGent>Maybe someone here can make some sense of that and figure out whats wrong :(
02:35:03  <theRealGent>no one? :(
02:36:06  * thlorenzquit (Remote host closed the connection)
02:36:39  * thlorenzjoined
02:40:50  * thlorenzquit (Ping timeout: 240 seconds)
02:42:40  <theRealGent>Please, any help or insight would be appreciated. I would think this of all places would be the best to get some helpful insight into this problem..
02:49:51  * lithiumjakequit (Ping timeout: 252 seconds)
02:51:52  * ednapiranhaquit (Quit: Leaving...)
02:59:13  * saibotvisadquit (Quit: Leaving.)
03:07:52  * Sorellaquit (Quit: It is tiem!)
03:12:29  * i_m_cajoined
03:15:13  * paulfryzelquit (Remote host closed the connection)
03:15:49  * jerrysvjoined
03:25:20  * i_m_caquit (Ping timeout: 265 seconds)
03:43:30  * jerrysvquit (Remote host closed the connection)
03:45:42  * jerrysvjoined
03:46:02  * saibotvisadjoined
04:19:37  * saibotvisadquit (Quit: Leaving.)
04:31:16  * brianloveswordsquit (Quit: Computer has gone to sleep.)
04:31:19  <levelbot>[npm] [email protected] <http://npm.im/dynalite>: A mock implementation of Amazon's DynamoDB built on LevelDB (@hichaelmart)
04:34:37  * mikealquit (Quit: Leaving.)
04:35:22  * mikealjoined
04:45:56  * jerrysvquit (Remote host closed the connection)
04:47:16  * paulfryzeljoined
04:51:51  * paulfryzelquit (Ping timeout: 265 seconds)
04:52:01  * dguttmanquit (Quit: dguttman)
04:58:25  * fritzyjoined
05:22:54  * theRealGentquit (Quit: theRealGent)
05:47:59  * paulfryzeljoined
05:52:45  * paulfryzelquit (Ping timeout: 265 seconds)
05:54:26  * rvaggquit (Ping timeout: 240 seconds)
05:59:46  * rvaggjoined
06:00:37  * ralphtheninjajoined
06:13:14  * fritzyquit
06:27:18  * ralphtheninjaquit (Ping timeout: 240 seconds)
06:48:24  * dominic_joined
06:48:44  * paulfryzeljoined
06:53:39  * paulfryzelquit (Ping timeout: 265 seconds)
07:33:29  * dominic_quit (Ping timeout: 252 seconds)
07:49:32  * paulfryzeljoined
07:54:04  * paulfryzelquit (Ping timeout: 265 seconds)
08:21:10  * kenan|afkchanged nick to kenansulayman
08:50:19  * paulfryzeljoined
08:54:58  * paulfryzelquit (Ping timeout: 265 seconds)
08:58:54  * sveisveijoined
09:50:59  * paulfryzeljoined
09:55:52  * paulfryzelquit (Ping timeout: 265 seconds)
10:03:06  * meschquit (Quit: Connection closed for inactivity)
10:51:08  * caolanmjoined
10:51:47  * paulfryzeljoined
10:52:20  <caolanm>what happens if a readStream is not read to completion, does the underlying iterator still get GC'd?
10:56:17  * paulfryzelquit (Ping timeout: 265 seconds)
11:09:24  <caolanm>seems the get closed if you close the db at least
11:52:04  * dominic_joined
11:52:33  * paulfryzeljoined
11:57:11  * paulfryzelquit (Ping timeout: 265 seconds)
12:05:04  * vijayeejoined
12:07:12  * thlorenzjoined
12:12:43  * thlorenzquit (Remote host closed the connection)
12:20:48  * dominic_quit (Ping timeout: 252 seconds)
12:21:08  * Sorellajoined
12:35:53  * thlorenzjoined
12:38:43  * mhernandez1joined
12:42:12  * dominic_joined
12:44:59  * vijayeequit (Ping timeout: 252 seconds)
12:46:58  * dominic_quit (Ping timeout: 265 seconds)
12:53:22  * paulfryzeljoined
12:56:42  * lithiumjakejoined
12:56:48  * brianloveswordsjoined
12:58:05  * paulfryzelquit (Ping timeout: 265 seconds)
12:59:10  * ednapiranhajoined
13:11:41  <rvagg>caolanm: hey, welcome!
13:12:01  <rvagg>caolanm: if you no longer have references to the readstream then it should be gced and the iterator closed
13:16:58  <rvagg>caolanm: so that goes for the underlying snapshot created by the iterator too, it should be automatically freed once the iterator is cleaned up; it's at the whim of the V8 GC *except* when it's in the middle of an async read in which case it's protected against premature gc, but that protection is undone as soon as we receive a value back into JS-land
13:17:36  <caolanm>rvagg: ok, so you have some mechanism for hooking into the GC process for v8 to free these things in c++ land?
13:18:29  <rvagg>caolanm: yeah, node gives us ObjectWrap that lets us make JS objects backed by C++ objects and it's all hooked in to the GC as normal JS objects
13:18:51  <caolanm>right, that's what I was looking for then
13:19:21  <rvagg>we just manage GC by adding to and removing from `Persistent` handles, kind of like putting them on the global scope, so we just carefully manage that process when it's important and leave normal GC up to the programmer
13:22:27  <caolanm>yeah, I noticed that but wasn't sure how thte GC was picking them up
13:22:44  <caolanm>I've not read much node with C++ code
13:22:53  <caolanm>thanks :)
13:26:44  <caolanm>rvagg: so, you also keep a record of all open iterators and close them when the db is closed?
13:27:03  <rvagg>caolanm: yes, we do that too
13:28:29  <caolanm>so, you open an interator, register it with the DB wrapper somehow, then close it if the readstream ends, or the stream is GCd or the db closes?
13:31:59  * thlorenzquit (Remote host closed the connection)
13:32:03  <rvagg>correct
13:36:45  <caolanm>thanks, I'll stop the dumb questions now ;)
13:49:16  * jjmalinajoined
13:54:03  * paulfryzeljoined
13:58:59  * paulfryzelquit (Ping timeout: 265 seconds)
14:05:20  * daviddiasjoined
14:10:17  * thlorenzjoined
14:11:09  * ramitosquit (Remote host closed the connection)
14:11:41  * ramitosjoined
14:26:37  * dguttmanjoined
14:26:47  * dguttmanquit (Client Quit)
14:32:49  * dguttmanjoined
14:37:46  * thlorenzquit (Remote host closed the connection)
14:38:04  * mikealquit (Quit: Leaving.)
14:46:10  * mhernandez1quit (Remote host closed the connection)
14:47:47  * mhernandez1joined
14:49:19  * thlorenzjoined
14:54:53  * paulfryzeljoined
14:59:19  * paulfryz_joined
14:59:24  * paulfryzelquit (Ping timeout: 265 seconds)
15:02:24  * jerrysvjoined
15:03:00  * daviddia_joined
15:04:26  * daviddiasquit (Ping timeout: 240 seconds)
15:09:09  * paulfryz_changed nick to paulfryzel
15:12:48  * mcavagejoined
15:16:02  * mikealjoined
15:17:25  * daviddia_quit (Remote host closed the connection)
15:17:59  * daviddiasjoined
15:22:02  * daviddiasquit (Ping timeout: 240 seconds)
15:40:39  * ednapiranhaquit (Remote host closed the connection)
15:44:00  * paulfryzelquit (Read error: Connection reset by peer)
15:44:32  * paulfryzeljoined
15:50:06  * mcavagequit (Ping timeout: 252 seconds)
15:52:43  * ednapiranhajoined
16:00:10  * ashihjoined
16:14:15  * mcavagejoined
16:29:20  * sveisveiquit (Quit: Connection closed for inactivity)
16:31:13  * paulfryzelquit (Read error: Connection reset by peer)
16:31:38  * paulfryzeljoined
16:35:48  <levelbot>[npm] [email protected] <http://npm.im/level-index-update>: A module to save a document into leveldb where the old indexes are removed in the same batch as the new ones are inserted (@binocarlos)
16:36:48  * ashihquit (Quit: Textual IRC Client: www.textualapp.com)
16:50:19  * paulfryzelquit (Read error: Connection reset by peer)
16:50:38  * paulfryzeljoined
17:01:43  * kenansulaymanchanged nick to kenan|afk
17:18:05  * thlorenzquit (Remote host closed the connection)