<    March 2017    >
Su Mo Tu We Th Fr Sa  
          1  2  3  4  
 5  6  7  8  9 10 11  
12 13 14 15 16 17 18  
19 20 21 22 23 24 25  
26 27 _2_8 29 30 31
00:47 cemerick joined
04:08 bturker joined
05:51 hive-mind joined
06:07 xiezhaowei joined
06:43 <xiezhaowei> hi, everyone, how to config the leveldb can get the best performance?
06:48 bturker joined
07:22 <DaJoe> that would depend greatly on how you define "performance" and :"best" as well as your expected workload and system resources
07:41 saurik joined
08:09 petro_ joined
08:29 <xiezhaowei> i want high concurrence, my server has 32 Core Cpu and 48G memory,I send 200 byte data per request, but it's just 12000/s
09:00 irsol joined
09:01 bturker joined
11:06 bturker joined
11:31 al-damiri joined
12:27 cemerick joined
13:00 tombriden joined
13:09 bturker joined
13:17 petro_ joined
15:28 Zor joined
15:42 bsparrow joined
15:49 Zor joined
15:56 cemerick joined
17:08 andyt1 joined
17:38 bturker joined
19:02 bturker joined
19:28 billstclair joined
19:41 codedmart_ joined
20:20 cemerick joined
20:46 cemerick joined
21:27 cmeik joined
21:57 flowpl joined
22:06 <flowpl> Hello everybody, I'm having quite a hard time to get a Riak cluster running on Kubernetes. Maybe somebody has pointers on what I'm doing wrong. I'm using this image: https://hub.docker.com/r/basho/riak-kv/, and by default, the containers start. The problem is, that it uses the IP as the nodename, so whenever Kubernetes reschedules or anything happens to any cluster member they get restarted with a different IP and I have to manually r
22:06 <flowpl> The natural next step would be to use the hostname as the nodename but then Riak wouldn't even start. I've tried the long hostname and the short form. Both versions can be resolved to the container's IP using dig.
22:19 flowpl_ joined
23:23 MJD joined