<     May 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  
28 29 30 31
00:09 masber joined
00:09 soveran joined
00:17 valhala_22 joined
00:19 valhala_22 joined
00:27 Cohedrin joined
00:38 valhala_22 joined
01:07 valhala_22 joined
01:16 edrocks joined
01:31 valhala_22 joined
01:50 nemothekid joined
01:51 garfed joined
02:04 tao joined
02:06 valhala_22 joined
02:13 soveran joined
02:19 roelmonnens joined
02:40 Cohedrin joined
02:59 wlightning-fuel joined
03:11 Cohedrin joined
03:18 edrocks joined
03:43 svm_invictvs joined
03:46 RemiFedora joined
03:46 wethu joined
04:15 soveran joined
04:50 fakenerd joined
04:53 Cohedrin joined
05:11 fakenerd joined
05:16 valhala_22 joined
05:19 enigma_raz joined
05:20 edrocks joined
05:41 valhala_22 joined
05:43 valhala_22 joined
05:46 enigma_r_ joined
05:52 valhala_22 joined
05:56 soveran joined
06:11 ogny joined
06:16 fakenerd joined
06:18 indistylo joined
06:24 enigma_raz joined
06:26 roelmonnens joined
06:32 tarkus joined
06:33 hos7ein joined
06:41 rendar joined
06:43 Majiir joined
06:46 rchavik joined
07:08 JohnnyRun joined
07:08 valkyr3e joined
07:26 fakenerd joined
07:46 huwenfeng joined
07:53 mikecmpbll joined
08:02 ogny joined
08:05 valhala_22 joined
08:11 cyborg-one joined
08:11 indistylo joined
08:15 DodgeThis joined
08:22 edrocks joined
08:25 galigan joined
08:35 tgy joined
08:35 <tgy> what's the best c++ client for redis ?
08:41 valhala_22 joined
08:42 Mr__Anderson joined
08:44 <minus> i've only ever used hiredis and can't exactly recommend it with C++. checking through the examples/repos of those listed here https://redis.io/clients#c-- seems like the thing to do
08:50 ntnn joined
08:51 Fabricio20 joined
08:52 akkad joined
08:53 yoavz joined
08:54 roelmonn_ joined
08:55 Dave_R joined
08:56 aruns joined
08:59 <minus> https://github.com/cylix/cpp_redis and https://github.com/hmartiro/redox seem to look best, both require C++11+
08:59 <minus> ^ tgy
09:02 <minus> first one seems somewhat neater to use, latter probably offers better performance
09:16 roelmonnens joined
09:23 brodolfo joined
09:45 AlienMayn joined
09:49 <badboy_> there's a redis client called redox? oO
09:52 <minus> what's so surprising about it, badboy_?
09:54 <badboy_> There's a operating system and kernel, written in Rust, called redox :D
09:54 <badboy_> that's what threw me off
10:14 robmozart joined
10:25 edrocks joined
11:05 shesek joined
11:10 valhala_22 joined
11:12 sz0 joined
11:23 WindChimes joined
11:44 mikecmpbll joined
11:50 WindChimes joined
12:03 valhala__ joined
12:14 conradev joined
12:14 Tux joined
12:14 Tux joined
12:14 rxc joined
12:14 jdiez joined
12:14 cbgbt joined
12:22 cmichel joined
12:24 dblessing joined
12:28 Mr__Anderson joined
12:54 edrocks joined
12:54 JohnnyRun joined
13:24 valhala_22 joined
13:34 daxelrod joined
13:49 valhala__ joined
13:51 fakenerd joined
13:57 valhala_22 joined
13:58 EyePulp joined
13:58 daxelrod joined
13:59 valhala__ joined
14:08 iamchrisf joined
14:14 wlightning-fuel joined
14:15 valhala_22 joined
14:16 shinnya joined
14:30 mdw joined
14:32 mikecmpb_ joined
14:43 winem_ joined
14:49 cyborg-one joined
14:56 finalbeta joined
15:02 Dave_R joined
15:09 wlightning-fuel joined
15:10 mikecmpbll joined
15:16 danns23 joined
15:20 danns23 joined
15:22 __Yiota joined
15:22 <__Yiota> what's the best way to healthcheck redis?
15:22 orbyt_ joined
15:28 Sarevok joined
15:30 jrgifford joined
15:34 valhala_22 joined
15:41 mikecmpbll joined
15:44 mikecmpbll joined
16:00 wlightning-fuel joined
16:00 raspado joined
16:11 gheegh joined
16:21 EyePulp joined
16:43 svm_invictvs joined
16:52 <badboy_> ping it
16:59 Cohedrin joined
17:08 edrocks joined
17:13 commonerror joined
17:13 hahuang65 joined
17:14 <commonerror> I'm working on a redirect service (based on query params) I'm thinking of storying serialized JSON in a list ["someRegx => http://example.com", ...]. Is there a better way to go about this?
17:22 iamchrisf joined
17:33 piklu_ joined
17:41 <GNU\colossus> you want to map ONE set of query parameters (=key) to ONE destination URL (=value)?
17:41 <GNU\colossus> or how is this supposed to work?
17:43 <commonerror> GNU\colossus: I'll be storing multiple regexp keys with destination values. For incoming HTTP requests, I'll be checking if any of the expressions pass and if they do I'll redirect to the destination.
17:44 <commonerror> In other words, the rewrite_rules List will be composed of a number of differing "regex => destination".
17:44 brodolfo joined
17:46 <GNU\colossus> and your list of redirect rules is so dynamic that you need that backed by redis?
17:46 <commonerror> Indeed it is
17:48 <commonerror> Heh, I could probably just have a form for admin to fill out that appends their redirect to a file and redeploys the service :D No one would be the wiser.
17:49 <GNU\colossus> I ask this because if you're not careful, your RE engine will end up compiling each resulting automaton anew for each incoming request and each stored regex.
17:52 <commonerror> I'm not sure what you mean by "compiling each resulting automation anew". Could you expand? It's not so dynamic that the list is having redirect appended every minute, it's more of a periodical update.
17:52 galigan joined
17:54 iamchrisf joined
18:00 Cohedrin joined
18:01 <GNU\colossus> commonerror, before a regular expression can match anything, it will be compiled into a DFA. that's why the POSIX RE has distinct compile and match functions. some runtimes (PHP, for instance) combine two steps (and transparently cache compiled REs)
18:01 <GNU\colossus> if your runtime isn't celver enough, it will probably parse and compile each of your REs for each match you want them to perform, even though the resulting RE/DFA hasn't changed
18:01 <GNU\colossus> in case you are serving loads of redirects, that might be a performance bottleneck of your service
18:02 <GNU\colossus> if you expect a few hundreds matches a second at most, just forget what I wrote
18:02 WindChimes joined
18:03 <commonerror> I'm looking at millions/second, but each of the REs will be unique. Granted, I don't expect to have more than a few 100 redirect rules in place at a given time.
18:06 WindChim_ joined
18:07 WindChi__ joined
18:07 fakenerd joined
18:09 daxelrod1 joined
18:12 Guest12483 joined
18:18 mikecmpbll joined
18:20 valhala_22 joined
18:22 jud^ joined
18:26 orbyt_ joined
18:28 mikecmpbll joined
18:36 __Yiota joined
18:41 finalbeta joined
18:46 minimalism joined
19:03 Cohedrin joined
19:09 fakenerd joined
19:13 rendar joined
19:13 rendar joined
19:14 mdw joined
19:15 sknebel joined
19:25 pandeiro joined
19:46 jud joined
19:53 WindChimes joined
20:14 Cohedrin joined
20:14 EyePulp joined
20:16 EyePulp joined
20:19 orbyt_ joined
20:27 <GNU\colossus> is it correct to use Redis replication (read-only slaves) to achieve read scalability? or will a massive write storm destroy read performance due to the replication trying to keep up regardless?
20:27 <Habbie> (1) yes (2) of course this is possible
20:29 <GNU\colossus> is there a general rule of thumb for an upper bound for the number of slaves?
20:31 Cohedrin joined
20:38 WindChim_ joined
20:40 edrocks joined
20:41 mikecmpb_ joined
21:05 nemothekid joined
21:18 chris11 joined
21:18 <chris11> what are some common reasons I'd get connection refused for localhost:6379?
21:19 <GNU\colossus> redis listens on a different port or interface. redis isn't running. redis has crashed, and isn't running any more. you have misconfigured your packet filter.
21:19 <minus> yes, if redis isn't running
21:19 <GNU\colossus> that about sums up the problem space
21:21 <chris11> ps aux | grep redis gives me this: 0:00 redis-server *:6379
21:21 <chris11> I am running redis from a docker container
21:21 <chris11> in a virtualbox
21:22 <xiaomiao> chris11: docker has its own network weirdness
21:22 <xiaomiao> most likely you're not in the same network namespace as the container
21:22 <chris11> ugh that's annoying
21:22 <xiaomiao> ... and I almost feel tempted to ask "why", but ... then I don't want to hear the answer ;)
21:24 <minus> chris11: so you need to connect to the ip of the redis container via the vbox vm
21:24 <minus> you can avoid docker giving containers a separate ip by disabling network isolation by passing --net=host to the docker run command
21:25 <minus> better just install linux on your host, and redis too
21:33 <__Yiota> chris11 try `redis-cli` from container
21:34 Dave_R joined
21:38 <chris11> connection refused.
21:39 <minus> docker exec my-container redis-cli?
21:39 <chris11> docker ps gives me>6379. I call localhost:6379 not localhost:32771, right?
21:40 <chris11> I'll try that
21:40 <chris11> still same error
21:42 <minus> you should go figure out how to use docker if you must use it
21:42 <chris11> you might have a point.
21:45 <chris11> so what's that command supposed to do? I read that its supposed to run a commad on the docker container. But I saw that I ran the command in the wrong spot so I reran it. I did not get any response. No error though.
21:48 Cohedrin joined
21:56 Cohedrin joined
21:59 WindChimes joined
22:18 nemothekid joined
22:19 Cohedrin joined
22:27 raspado joined
22:33 Fabricio20 joined
22:34 hahuang65 joined
22:34 dh01 joined
22:37 codepython777 joined
22:41 WindChimes joined
22:44 dh1tw joined
22:49 shinnya joined
22:59 ChrisJames02170 joined
23:02 pandeiro joined
23:13 codepython777 joined
23:23 valhala_22 joined
23:25 KennethWilke joined
23:30 berken joined
23:33 Cohedrin joined
23:37 Cohedrin joined