00:29:42  * jerrysvquit (Remote host closed the connection)
01:59:19  * neonstalwartjoined
03:52:44  * dguttmanquit (Ping timeout: 245 seconds)
04:18:35  * neonstalwartquit (Quit: Leaving.)
05:34:21  * owen1part ("WeeChat 1.1-dev")
05:49:09  * bensternthalquit (Ping timeout: 272 seconds)
05:53:53  * bensternthaljoined
08:20:11  * bonswouarjoined
09:52:23  * joakinojoined
12:30:30  * tarrudajoined
13:09:03  * bonswouarquit (Ping timeout: 250 seconds)
13:09:36  * bonswouarjoined
14:46:51  * neonstalwartjoined
15:49:25  * dguttmanjoined
16:25:09  * jerrysvjoined
16:28:56  * binocarlosjoined
16:38:11  * tarrudaquit (Ping timeout: 252 seconds)
17:16:01  * darngeekjoined
17:22:02  * binocarlosquit (Ping timeout: 246 seconds)
17:25:23  * Tommasojoined
17:26:06  * bonswouarquit (Remote host closed the connection)
17:34:15  <Tommaso>hey
17:34:56  * Tommasochanged nick to tommo
17:36:36  * tommoquit (Quit: Leaving)
17:39:31  * tommojoined
17:39:53  <tommo>hey all
17:40:46  <tommo>I have a problem that might require modifying LevelDB, so I thought to ask first to someone who knows better
17:41:37  <tommo>basically, our mobile app can be terminated at any time, so I want to constantly evict stuff from the cache in order to minimize how long it takes to flush it when the app is kileld
17:41:40  <tommo>*killed
17:42:22  <tommo>the cache is 20MB now, and if it happens to want to compact the database it can take a pretty long time, long enough sometimes to make iOS kill it
17:45:33  <tommo>as far as I can see, the only way is to modify leveldb myself to let the cache do this?
17:56:47  * binocarlosjoined
18:17:50  <rescrv>tommo: write=sync will ensure that if your app terminates (even kill -9 or the ios equiv), the data will be present when you reopen
18:18:10  <rescrv>tommo: even writing without write=sync will guarantee it on POSIX platforms, but I don't know about iOS
18:18:46  <rescrv>and there's a difference between "cache" and "write_buffer". You'll want to tune the write_buffer to force stuff out to disk more often
18:19:21  <tommo>uhm, ok
18:20:33  <tommo>I meant the cache though, are the entries in it constantly written-through?
18:22:24  <tommo>if write=sync?
18:22:55  * darngeekquit (Quit: Leaving)
18:37:45  * dcbjoined
18:52:02  * binocarlosquit (Ping timeout: 244 seconds)
18:57:17  * tarrudajoined
19:30:48  * tommoquit (Ping timeout: 245 seconds)
19:35:28  * joakinoquit
19:49:53  * binocarlosjoined
20:18:23  * neonstalwartquit (Ping timeout: 265 seconds)
20:35:48  * binocarlosquit (Ping timeout: 245 seconds)
21:03:29  * neonstalwartjoined
22:04:01  * tommojoined
22:14:01  * tommoquit (Quit: Leaving)
22:38:43  * tarrudaquit (Ping timeout: 245 seconds)
23:17:27  * yyyjpjoined
23:21:05  <yyyjp>hello. i'm new to leveldb, only started playing with it yesterday. it's great! i've only previously used mongodb, which i found easy to get my head around, but i really love the idea that you can store the db to a file on disk with leveldb. i'm trying to figure out if leveldb would be suitable for an API server that needs to store things like users, posts, channels etc, and tie those bits of information together.
23:21:13  <yyyjp> i'm not sure if levelup and sublevel facilitates everything i need.
23:22:24  <yyyjp>what i would have previously done with mongodb, i'd have a collection for users, a collection for posts, and a collection for channels, and the documents in those collections can reference other documents from other collections when I need to have something specific returned (ie. return all posts this user has posted within this channel)
23:22:49  <yyyjp>is leveldb remotely suitable for something like this, or am i way off the mark?
23:28:50  * tdfischerquit (Quit: No Ping reply in 180 seconds.)
23:29:22  * tdfischerjoined
23:39:07  * dcbquit (Ping timeout: 250 seconds)
23:44:18  * neonstalwartquit (Quit: Leaving.)