- [00:01] wmage (~wmage@nat-88-212-40-142.antik.sk) joined #redis.
- [00:05] stask312 (~stask312@212.25.110.130) joined #redis.
- [00:14] <temoto> How to truncate set to N lowest items?
- [00:14] <temoto> sort foo limit 0 2 store foo works, but it changes type from set to list.
- [00:15] <temoto> How do i convert key from list to set again?
- [00:26] Geffy (~geoffgars@2a02:40:2:0:e9c6:8dc3:dcbd:41b5) joined #redis.
- [00:29] _macro (~Neil@c-71-204-169-22.hsd1.ca.comcast.net) joined #redis.
- [00:39] wmage (~wmage@nat-88-212-40-142.antik.sk) left irc: Read error: Connection reset by peer
- [00:39] versicolor (~quassel@46.10.10.206) left irc: Remote host closed the connection
- [00:42] jrydberg_ (~jrydberg@81-235-188-3-no48.tbcn.telia.com) joined #redis.
- [00:43] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) joined #redis.
- [00:47] p1d (~p1d@ns1.vonaffenfels.de) joined #redis.
- [00:47] <Garo_> how I can get the number of buckets and other details which the main dictionary, or a non-zipmap hash item has?
- [00:48] insin (~insin@host86-148-254-166.range86-148.btcentralplus.com) joined #redis.
- [00:48] kppullin (~kppullin@pdpc/supporter/active/kppullin) joined #redis.
- [00:49] <Garo_> for example the dict.c has _dictPrintStatsHt, but that doesn't seem to be called from anywhere :(
- [00:51] wilmoore (~wilmoore@c-67-190-17-108.hsd1.co.comcast.net) left irc: Ping timeout: 248 seconds
- [00:52] agentzh (~agentz@nginx/adept/agentzh) joined #redis.
- [00:56] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) left irc: Quit: martincozzi
- [01:01] ambroff (~ambroff@c-24-4-207-161.hsd1.ca.comcast.net) left irc: Quit: ambroff
- [01:09] rittyan (~rittyan@2a02:6b8:0:40c:7aca:39ff:feb3:d779) joined #redis.
- [01:30] thehodge (~thehodge@2001:470:1f09:13a3:8d67:f348:1929:4a34) joined #redis.
- [01:33] nopz___ (~nopz___@8.14.117.35) joined #redis.
- [01:38] wmage (~wmage@nat-88-212-40-142.antik.sk) joined #redis.
- [01:49] drbobbeaty (~drbobbeat@c-67-184-75-162.hsd1.il.comcast.net) joined #redis.
- [01:55] xer0x (~xer0x@S0106000625746e56.vc.shawcable.net) joined #redis.
- [02:03] npmapn (~quassel@188.26.62.233) joined #redis.
- [02:06] xer0x (~xer0x@S0106000625746e56.vc.shawcable.net) left irc: Quit: Leaving...
- [02:12] solaries_ (~solaries@ppp-188-174-0-167.dynamic.mnet-online.de) joined #redis.
- [02:12] <solaries_> hi all
- [02:13] <solaries_> is it possible to expire a key in a way that it also expires other keys?
- [02:13] <solaries_> or better: if "x" is expired I want to remove "x" from a set "s"
- [02:16] thehodge (~thehodge@2001:470:1f09:13a3:8d67:f348:1929:4a34) left irc: Remote host closed the connection
- [02:16] thehodge (~thehodge@cpc5-seac20-2-0-cust310.7-2.cable.virginmedia.com) joined #redis.
- [02:20] thehodge (~thehodge@cpc5-seac20-2-0-cust310.7-2.cable.virginmedia.com) left irc: Ping timeout: 240 seconds
- [02:25] nawtnow (~nawt@c-50-132-9-148.hsd1.wa.comcast.net) joined #redis.
- [02:25] drbobbeaty (~drbobbeat@c-67-184-75-162.hsd1.il.comcast.net) left irc: Quit: drbobbeaty
- [02:26] versicolor (~quassel@46.10.10.206) joined #redis.
- [02:28] nawt (~nawt@c-50-132-9-148.hsd1.wa.comcast.net) left irc: Ping timeout: 268 seconds
- [02:29] kushal (~kdas@fedora/kushal) left irc: Ping timeout: 255 seconds
- [02:34] klausweiss (~user@78.104.162.153) joined #redis.
- [02:34] thehodge (~thehodge@82.109.33.196) joined #redis.
- [02:46] kushal (~kdas@fedora/kushal) joined #redis.
- [03:00] lux___ (~lux@ppp-80-75.25-151.libero.it) joined #redis.
- [03:00] NetRoY (~NetRoY@nat/yahoo/x-uljezwvvpyiacgsc) left irc: Quit: NetRoY
- [03:05] __alex (~alex@g230192252.adsl.alicedsl.de) joined #redis.
- [03:11] X99 (~quassel@218.77.14.195) left irc: Read error: Connection reset by peer
- [03:14] chakrit (~chakrit@ppp-58-8-98-21.revip2.asianet.co.th) left irc: Quit: chakrit
- [03:14] solaries_ (~solaries@ppp-188-174-0-167.dynamic.mnet-online.de) left irc: Read error: Operation timed out
- [03:15] kushal (~kdas@fedora/kushal) left irc: Ping timeout: 255 seconds
- [03:18] xjiujiu (~quassel@218.77.14.195) joined #redis.
- [03:24] Nuck -> NuckOff
- [03:24] xjiujiu (~quassel@218.77.14.195) left irc: Read error: Connection reset by peer
- [03:25] __alex (~alex@g230192252.adsl.alicedsl.de) left irc: Ping timeout: 240 seconds
- [03:26] awksedgreep (~awksedgre@c-24-98-243-58.hsd1.ga.comcast.net) joined #redis.
- [03:28] xjiujiu (~quassel@218.77.14.195) joined #redis.
- [03:29] wmage (~wmage@nat-88-212-40-142.antik.sk) left irc: Read error: Connection timed out
- [03:29] Geffy (~geoffgars@2a02:40:2:0:e9c6:8dc3:dcbd:41b5) left irc: Quit: leaving
- [03:40] jonesy (~jonesy@pool-173-71-115-162.cmdnnj.fios.verizon.net) left irc: Quit: Computer has gone to sleep.
- [03:41] drbobbeaty (~drbobbeat@38.98.137.29) joined #redis.
- [03:45] ron (~ron@unaffiliated/ron) left irc: Ping timeout: 240 seconds
- [03:47] getxsick_ (xsx@tramwaj.asi.pwr.wroc.pl) joined #redis.
- [03:48] getxsick (xsx@unaffiliated/getxsick) left irc: Read error: Operation timed out
- [03:48] Wombert (~Wombert@dslb-088-065-201-187.pools.arcor-ip.net) joined #redis.
- [03:48] ron (~ron@unaffiliated/ron) joined #redis.
- [03:49] mbuf (user@nat/redhat/x-bwflrestueamtlou) joined #redis.
- [03:49] <mbuf> is there a way to undefine or unset a value that has been set using SET?
- [03:49] d0k (~d0k@p5B3B1342.dip.t-dialin.net) joined #redis.
- [03:51] wmage (~wmage@nat-88-212-40-142.antik.sk) joined #redis.
- [03:54] <mbuf> never mind, used setex
- [03:57] willpierce (~willp@c-76-103-214-4.hsd1.ca.comcast.net) left irc: Quit: ircII EPIC4-2.10.1 -- Are we there yet?
- [03:57] TimTim (TimTim@cpe-098-026-149-108.triad.res.rr.com) joined #redis.
- [04:01] nu7hatch_ (~cubox@r186-48-237-57.dialup.adsl.anteldata.net.uy) joined #redis.
- [04:01] mbuf (user@nat/redhat/x-bwflrestueamtlou) left #redis ("ERC Version 5.3 (IRC client for Emacs)").
- [04:01] TimTim (TimTim@cpe-098-026-149-108.triad.res.rr.com) left irc: Ping timeout: 248 seconds
- [04:04] nu7hatch (~cubox@r186-48-244-75.dialup.adsl.anteldata.net.uy) left irc: Ping timeout: 248 seconds
- [04:04] nu7hatch_ -> nu7hatch
- [04:08] wmage (~wmage@nat-88-212-40-142.antik.sk) left irc: Read error: Connection timed out
- [04:09] alekx (4e61605a@gateway/web/freenode/ip.78.97.96.90) joined #redis.
- [04:10] Frippe (~Frippe@unaffiliated/frippe) joined #redis.
- [04:24] klausweiss (~user@78.104.162.153) left irc: Ping timeout: 240 seconds
- [04:35] nsalvo (~nsalvo@190.55.32.117) joined #redis.
- [04:36] ron (~ron@unaffiliated/ron) left irc: Ping timeout: 248 seconds
- [04:40] xetorthio (~jleibiusk@200.41.238.50) joined #redis.
- [04:59] ron (~ron@unaffiliated/ron) joined #redis.
- [05:05] Jrz (~jrz@87.239.184.141) joined #redis.
- [05:05] PiotrSikora (~none@nginx/adept/piotrsikora) left irc: Excess Flood
- [05:06] PiotrSikora (~none@nginx/adept/piotrsikora) joined #redis.
- [05:10] soveran (~soveran@186.19.214.247) joined #redis.
- [05:11] nsalvo (~nsalvo@190.55.32.117) left irc: Ping timeout: 240 seconds
- [05:14] antirez (~antirez@host240-18-dynamic.9-79-r.retail.telecomitalia.it) joined #redis.
- [05:14] #redis: mode change '+v antirez' by ChanServ!ChanServ@services.
- [05:16] <alekx> antirez: I'll be here in 2 minute
- [05:16] <antirez> alekx: no hurry I'm here for some time
- [05:20] <alekx> back
- [05:20] <alekx> antirez: both those "problems" made me think of SLAs
- [05:21] <alekx> bascially by allowing the client to specify a "timeout" you'd move the switch responsibility to the side in control
- [05:21] <alekx> key * timeout 10
- [05:21] <alekx> would translate to: if I don't get all keys in 10seconds please cut me off
- [05:22] <antirez> alekx: I'm not sure this solves the real issue here
- [05:22] <antirez> alekx: when I ask for a big range of objects, I'm ok with using some more time
- [05:22] <alekx> a client that would know is going to execute an expensive operation would set the timeout accordingly and would be aware of the implications
- [05:23] <alekx> antirez: how would you formulate the real issue?
- [05:23] <antirez> alekx: this is impossible from the point of view of the implementaiton
- [05:23] <antirez> alekx: imagine this:
- [05:23] <antirez> alekx: I send N different commands, like: LRANGE foo bar TIMEOUT 5
- [05:23] <antirez> and in a pipeline many different commands
- [05:23] <antirez> similar to that, with different timeouts
- [05:23] <antirez> all the output objects get mixed in the output buffer
- [05:24] <antirez> there is no way to tell what was transferred and what not
- [05:24] <antirez> even if, it would be possible
- [05:24] <antirez> the problem we are trying to solve here is different
- [05:24] <antirez> for Pub/Sub, is the slow receiver, and there is no way for it to set a timeout
- [05:24] <alekx> antirez: in the pipeline model the timeout would be set at the pipeline level and not at command level
- [05:24] <antirez> alekx: there is no "pipeline level". Pipeline != MULTI/EXEC
- [05:25] <antirez> but, even semantically
- [05:25] <antirez> it's not correct that the client is forced to set a timeout
- [05:25] <alekx> antirez: when he subscribes he could provide a timeout
- [05:25] <antirez> clients don't have control about the network bandwidth
- [05:25] <alekx> antirez: not force... but has the option to
- [05:25] <antirez> yes but this opinion is semantically misleading IMHO
- [05:25] <antirez> because
- [05:25] <antirez> 1) The client can send a bad TIMEOUT (too long) or not send it at all.
- [05:26] <alekx> antirez: semantically it is: give me the response in 10 seconds or nothing
- [05:26] <antirez> and still will make the server crashing
- [05:26] <antirez> so, what was our goal, that was protecting the server against "bad" clients, is not reached
- [05:26] <alekx> antirez: but the responsibility is on his side
- [05:26] <antirez> responsible of crashing the server
- [05:26] <alekx> antirez: a client could always make the server missbehave
- [05:26] <antirez> here the point is: avoid that a client that is doing wrong things can crash the server
- [05:26] <antirez> yes but on purpose
- [05:27] <antirez> here instead, the client can make the server misbehave without intention
- [05:27] <antirez> just because it is making too many objects accumulating in the output buffer
- [05:27] <alekx> antirez: you could have a set of default timeout (configurable)
- [05:27] <antirez> we need to protect against this
- [05:27] <antirez> that's bad as well
- [05:27] <antirez> a client in a slow network is perfectly free to ask 10k objects and read it with some time
- [05:27] <antirez> the problem is not the time ,but the space taken
- [05:28] <alekx> antirez: that's Redis internal problem
- [05:28] <alekx> it's not an application/client problem
- [05:28] <antirez> yes, but that's issue #93 :)
- [05:28] <alekx> LOL :)
- [05:28] <antirez> Redis needs to close clients that have an output buffer getting bigger and bigger
- [05:28] <antirez> but I think that it is better to don't fix the issue about LRANGE / KEYS / ...
- [05:29] <antirez> this is hard to fix well, more likely we'll create problems trying to fix that
- [05:29] <antirez> instead, the Pub/Sub thing is very common
- [05:29] <antirez> the producer is faster than the consumer…. and booom
- [05:29] <antirez> also, Pub/Sub is "push"
- [05:29] <antirez> so the client will receive data without asking with a command
- [05:29] <alekx> I've discussed this problem a while ago with some experts in the field
- [05:30] <alekx> and looked at different approaches... you know what the final advise was?
- [05:30] <antirez> I guess, close connection when N pending messages?
- [05:30] <alekx> this is an unsolvable problem... move the responsibility to the party that can make the smartest decision
- [05:31] <antirez> yes, in this respect it is Redis
- [05:31] <antirez> alternatively
- [05:31] <alekx> closing a connection with N pending messages is not an "educated decision"
- [05:31] <antirez> there is to implement flow control
- [05:31] <antirez> I think so actually
- [05:31] <alekx> at least if the client is not informed or cannot change that
- [05:31] <antirez> flow control is what an engineer will call "the right thing". But does not work properly
- [05:32] <antirez> it means to start advising the publisher that it is publishing too fast
- [05:32] <alekx> I think I've lost you re: flow contorl
- [05:32] <antirez> flow control is a way to add in the protocol informations that the different parties can use to auto-regulate the flow
- [05:32] <antirez> so
- [05:32] <alekx> I don't think I agree
- [05:32] rittyan (~rittyan@2a02:6b8:0:40c:7aca:39ff:feb3:d779) left irc: Remote host closed the connection
- [05:32] <antirez> the receiver will start getting messages like" you are too slow"
- [05:32] <alekx> there's not a too fast publisher... it's just a slow subscriber
- [05:32] <antirez> the publisher will start getting messages like "you are publishing too fast"
- [05:33] <antirez> ok but how would you solve the issue?
- [05:33] <antirez> there are only two solutions:
- [05:33] <antirez> 1) create less messages or.
- [05:33] <antirez> 2) enlarge the queue
- [05:33] <alekx> 1) you cannot create less messages
- [05:33] <antirez> but "2" is bad as not just memory is consumed, also delay is added
- [05:33] <alekx> or I'm missing something
- [05:34] <antirez> alekx: what you do is to advice the publisher that its messages are not processed fast enough
- [05:34] <antirez> alekx: it is up to the application to decide WHAT to do
- [05:34] <alekx> antirez: correct
- [05:34] <antirez> yes, but I don't like such a "right" approach
- [05:35] <antirez> IMHO closing the connection is simpler, raw, but better
- [05:35] <alekx> well... then why not dropping messages
- [05:35] <antirez> at least from the point of view of Redis Pub/Sub that is fire and forget
- [05:35] <antirez> alekx: because no one will notice
- [05:35] <alekx> you notify
- [05:35] <antirez> this is a form of flow control, then
- [05:36] <alekx> you have a special response... dropped N messages
- [05:36] <antirez> yes this is a solution indeed, and is a flow control implemented in a different way
- [05:36] <antirez> I don't like it personally, but is definitely a solution
- [05:36] <antirez> but for this to work
- [05:36] <antirez> you need a networking layer that is also able to "insert" messages before the messages pending
- [05:36] <antirez> since your control message "you are too slow, messages dropped"
- [05:36] <antirez> has to jump the current queue
- [05:36] <antirez> and be transmitted ASAP
- [05:37] <antirez> Redis can't do that from the point of view of internals btw
- [05:37] <antirez> (but I would not implement it anyway)
- [05:37] <antirez> but yes, this was among the solutions we checked
- [05:37] <antirez> but...
- [05:37] <antirez> if we were able to insert messages
- [05:38] <antirez> I would definitely inject a special message before dropping the connection in my current planned solution
- [05:38] <antirez> "we are exiting since you have a long queue"
- [05:38] <antirez> otherwise the client will not be able to tell if it is a networking issue, or it is too slow
- [05:38] <alekx> I understand it is an implementation "issue" but I definitely find it more "friendly" then cutting a client off
- [05:38] <antirez> agreed, but this would require extreme modifications in the Redis internals
- [05:39] <antirez> not something we can do now unfortunately
- [05:39] <alekx> antirez: I confess I don't like at all the idea of cutting off a client connection
- [05:39] <alekx> on the other hand I do understand what you are saying
- [05:39] <antirez> it is the kind of problem where good solutions are complex and require even that the participants are able to handle the control messages you send
- [05:39] <antirez> so we can start with this hard solution
- [05:39] <alekx> well I guess the ideal would be a solution that uses all these strategies
- [05:39] <antirez> and see what users report...
- [05:40] <alekx> but it might be an overkill implementation wise
- [05:40] <antirez> btw fixing this in this way also fixes half of the problem
- [05:40] <antirez> because with Pub/Sub we are ok, no slow receiver can cause out of memory
- [05:40] <antirez> but then there is LPUSH/BLPOP side of the matter
- [05:40] <antirez> Resque & Co
- [05:40] <antirez> in this case, we can't close connections or alike, data goes into a list
- [05:41] <antirez> but
- [05:41] <antirez> at least… LPUSH will return the current list length
- [05:41] <antirez> so it is a form of basic message the "publisher" receives
- [05:42] nsalvo (~nsalvo@190.55.32.117) joined #redis.
- [05:42] <alekx> this might not make a lot of sense... but let me throw it out
- [05:42] <alekx> memory being the issue here
- [05:42] <alekx> what if these slow processing clients are penalized/slowed down by removing their data from the memory
- [05:43] <alekx> basically: you are too slow/consuming my messages too slow, I'm spilling these over to disk
- [05:43] <alekx> I'll continue to serve you, but until you don't show me you can consume at a high rate... I'm going to be slow too
- [05:45] <antirez> alekx: RabbitMQ does this and even more, for Redis we want really a simple solution
- [05:46] <alekx> antirez: well I guess then simple would mean either dropping messages or closing connection
- [05:46] <antirez> alekx: yes, I think so...
- [05:46] <alekx> but it will be a solution particular to this scenario only
- [05:46] <antirez> what is better is not clear
- [05:47] <alekx> and I don't think you can make consistent over the 3 different scenarios
- [05:47] <antirez> if we drop the client
- [05:47] <alekx> 1) pub/sub; 2) long pipelined commands; 3) BLPOP
- [05:47] <antirez> with the current PUBLISH semantics we get some info back
- [05:47] <antirez> since PUBLISH returns the number of clients that (locally) received the message
- [05:48] <antirez> if we discard the message, we can still return something back
- [05:48] <antirez> but my concern is, resistance
- [05:48] <antirez> that is
- [05:48] <antirez> if a client got blocked for a software error
- [05:48] <antirez> dropping the connection is much better
- [05:48] <antirez> it will likely start again
- [05:48] <antirez> dropping connection instead will cause it to remain blocked forever
- [05:48] <alekx> antirez: you do not know that
- [05:49] <antirez> well it is more likely that if we close the connection read() will return 0 and the client will exit
- [05:49] <alekx> antirez: I could tell you.. what if I'm processing more data on my machine between 2-4am and that's why I'll be slow
- [05:49] <alekx> but I don't want you to disconnect me
- [05:49] <antirez> and it is 100% guaranteed that if we just drop messages the receiver will never un block
- [05:50] <antirez> alekx: the "window" I suggest makes it a bit more flexible, and will not drop your connection in 2 seconds
- [05:50] <antirez> but will require 10 seconds of going over the limit
- [05:50] <antirez> this is why I don't want to implement the "close on MAX reached" as other systems implement
- [05:50] <alekx> basically you are referring yourself at a timeout
- [05:50] <alekx> server side default timeout
- [05:50] <antirez> it is not a timeout, it is:
- [05:51] <antirez> if you are over the MAX for N seconds, then I close you
- [05:51] <antirez> that is better than: if you reached MAX I close
- [05:51] <antirez> what we pay is: 10 seconds delay in our reaction
- [05:51] <alekx> it is definitely better
- [05:51] <antirez> but what we gain is: avoiding a lot of useless connections cloesd
- [05:51] <antirez> closed
- [05:51] elcuervo (~elcuervo@r186-48-237-57.dialup.adsl.anteldata.net.uy) joined #redis.
- [05:52] <alekx> and I think what I've suggested would have been even better from a client perspective
- [05:52] <alekx> let the client tell you how fast to cut it off after the threshold is reached
- [05:52] <alekx> I can imagine numerous scenarios in which client side processing would vary over time making the client either lag behind or catching up
- [05:53] <alekx> antirez: so I'd do something like this
- [05:53] <antirez> I think that since the server is affected (crash) this should not be decided by the client, this is why I disagree
- [05:53] <alekx> default setting: if you reach MAX I'll cut your connecting in X seconds
- [05:53] <alekx> but I'm allowing you (the client) to specify your own Y seconds
- [05:54] <antirez> not good, clients will specify 9999 and the server will crash
- [05:54] <antirez> we need to protect the server FROM clients :)
- [05:54] <antirez> the 10 seconds figure is not random
- [05:54] <antirez> at peak PUBLISH speed, 150k/s
- [05:54] <antirez> it means 1500000 messages
- [05:54] <antirez> that are a few hundreds of megabytes
- [05:54] <antirez> more than this is too much
- [05:55] <alekx> it is a random number as it depends on what that machine is doing and its hw
- [05:55] <antirez> no I mean: with 10 seconds you have a max amount of memory you can use for misbehaving clients
- [05:55] <alekx> if I have a 64GB machine I might not care about 1G
- [05:55] <antirez> if the client tells you the timeout, you don't have any guarantee
- [05:55] <antirez> alekx: then we should make the "10 seconds" configurable
- [05:56] <antirez> but server side anyway
- [05:56] <alekx> antirez: that's better already
- [05:56] <alekx> :D
- [05:56] <antirez> the problem is that there were discussions in the mailing list about exposing two config options to the users
- [05:56] <antirez> for the user the concept of "close if MAX is reached" is much simpler
- [05:57] <alekx> lemme grab a coffee and reanalyze my arguments
- [05:57] <antirez> ;)
- [05:57] <antirez> I'm going back coding now
- [05:57] <antirez> but please if you want send a message in the ML
- [05:57] <antirez> to contribute to the discussion
- [05:57] <antirez> I'll wait a few days before implementing this
- [05:57] <antirez> it is not clear what is going to be the best solution, currently
- [05:57] <antirez> so it's not a closed deal
- [05:57] <antirez> :)
- [05:57] <alekx> it's easier to exchange ideas live... as I can get feedback righ away
- [05:57] <antirez> later! And thanks for the ideas
- [05:58] <alekx> we could do another session tomorrow
- [05:58] <alekx> take care!
- [05:58] <antirez> ok :) Ciao
- [06:00] superjudge (~superjudg@195.22.80.141) joined #redis.
- [06:10] seppo0010 (~Adium@200.69.194.105) joined #redis.
- [06:11] arnee (~arnee@a89-183-23-88.net-htp.de) joined #redis.
- [06:12] napperjabber (~napperjab@149.48.161.10) joined #redis.
- [06:16] seppo0010 (~Adium@200.69.194.105) left #redis.
- [06:18] rittyan (~rittyan@2a02:6b8:0:40c:7aca:39ff:feb3:d779) joined #redis.
- [06:19] solaries_ (~solaries@ppp-188-174-0-167.dynamic.mnet-online.de) joined #redis.
- [06:20] rittyan (~rittyan@2a02:6b8:0:40c:7aca:39ff:feb3:d779) left irc: Remote host closed the connection
- [06:20] jonesy (~jonesy@68.64.144.221) joined #redis.
- [06:22] Sarevok (~locke@rrcs-98-101-176-143.midsouth.biz.rr.com) joined #redis.
- [06:22] Axsuul (~Axsuul@75-140-75-52.dhcp.mtpk.ca.charter.com) left irc: Ping timeout: 240 seconds
- [06:22] xjiujiu (~quassel@218.77.14.195) left irc: Read error: Connection reset by peer
- [06:29] agentzh (~agentz@nginx/adept/agentzh) left irc: Quit: Leaving.
- [06:32] lux_ (~lux@ppp-136-117.25-151.libero.it) joined #redis.
- [06:33] lux_ -> Guest69310
- [06:35] lux___ (~lux@ppp-80-75.25-151.libero.it) left irc: Ping timeout: 240 seconds
- [06:38] arnee (~arnee@a89-183-23-88.net-htp.de) left irc: Remote host closed the connection
- [06:40] superjudge (~superjudg@195.22.80.141) left irc: Quit: superjudge
- [06:43] Wombert (~Wombert@dslb-088-065-201-187.pools.arcor-ip.net) left irc: Quit: Wombert
- [06:47] xetorthio (~jleibiusk@200.41.238.50) left irc: Ping timeout: 240 seconds
- [06:53] lux___ (~lux@ppp-144-121.25-151.libero.it) joined #redis.
- [06:56] solaries_ (~solaries@ppp-188-174-0-167.dynamic.mnet-online.de) left irc: Ping timeout: 240 seconds
- [06:56] Guest69310 (~lux@ppp-136-117.25-151.libero.it) left irc: Ping timeout: 276 seconds
- [06:58] elcuervo (~elcuervo@r186-48-237-57.dialup.adsl.anteldata.net.uy) left irc: Ping timeout: 240 seconds
- [07:00] arnee (~arnee@a89-183-23-88.net-htp.de) joined #redis.
- [07:00] arnee (~arnee@a89-183-23-88.net-htp.de) left irc: Remote host closed the connection
- [07:10] elcuervo (~elcuervo@r186-48-242-66.dialup.adsl.anteldata.net.uy) joined #redis.
- [07:14] macabre (~macabre@63.133.215.18) joined #redis.
- [07:15] el_kevin_ (~el_kevino@216.249.7.209.tor.pathcom.com) joined #redis.
- [07:16] el_kevino (~el_kevino@216.249.7.209.tor.pathcom.com) left irc: Read error: Connection reset by peer
- [07:21] lux___ (~lux@ppp-144-121.25-151.libero.it) left irc: Quit: This computer has gone to sleep
- [07:24] agile (~mike@71-86-124-96.dhcp.ftwo.tx.charter.com) left irc: Ping timeout: 240 seconds
- [07:28] elcuervo (~elcuervo@r186-48-242-66.dialup.adsl.anteldata.net.uy) left irc: Remote host closed the connection
- [07:28] CoffeeIV (~rgr@rrcs-71-42-183-81.sw.biz.rr.com) left irc: Read error: Operation timed out
- [07:39] agile (~mike@71-86-124-96.dhcp.ftwo.tx.charter.com) joined #redis.
- [07:46] rittyan (~rittyan@2a02:6b8:0:40c:7aca:39ff:feb3:d779) joined #redis.
- [07:48] elcuervo (~elcuervo@r186-48-242-66.dialup.adsl.anteldata.net.uy) joined #redis.
- [07:53] solaries1 (~solaries@ppp-188-174-0-167.dynamic.mnet-online.de) joined #redis.
- [07:57] el_kevin_ (~el_kevino@216.249.7.209.tor.pathcom.com) left irc: Remote host closed the connection
- [07:58] el_kevino (~el_kevino@216.249.7.209.tor.pathcom.com) joined #redis.
- [08:07] xer0x (~xer0x@S0106000625746e56.vc.shawcable.net) joined #redis.
- [08:11] steph021 (~steph021@unaffiliated/steph021) joined #redis.
- [08:11] p1d (~p1d@ns1.vonaffenfels.de) left irc: Quit: ...
- [08:12] CoffeeIV (~rgr@dsl093-217-226.aus1.dsl.speakeasy.net) joined #redis.
- [08:12] versicolor (~quassel@46.10.10.206) left irc: Ping timeout: 240 seconds
- [08:12] versicolor (~quassel@46.10.10.206) joined #redis.
- [08:16] tjholowaychuk (~tjholoway@S010658b03565e6c6.gv.shawcable.net) joined #redis.
- [08:18] xer0x (~xer0x@S0106000625746e56.vc.shawcable.net) left irc: Quit: Leaving...
- [08:21] getxsick_ -> getxsick
- [08:21] wilmoore (~wilmoore@c-67-190-17-108.hsd1.co.comcast.net) joined #redis.
- [08:22] Jrz (~jrz@87.239.184.141) left irc: Quit: Computer has gone to sleep.
- [08:23] adammck (~adammck@206.217.95.186) joined #redis.
- [08:26] rittyan (~rittyan@2a02:6b8:0:40c:7aca:39ff:feb3:d779) left irc: Ping timeout: 252 seconds
- [08:28] TimTimTim (TimTim@cpe-098-026-149-108.triad.res.rr.com) joined #redis.
- [08:28] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) joined #redis.
- [08:28] antirez (~antirez@host240-18-dynamic.9-79-r.retail.telecomitalia.it) left irc: Quit: antirez
- [08:30] daniel_karlsson (~kardan@c83-254-118-140.bredband.comhem.se) joined #redis.
- [08:31] daniel_karlsson (~kardan@c83-254-118-140.bredband.comhem.se) left irc: Client Quit
- [08:34] solaries1 (~solaries@ppp-188-174-0-167.dynamic.mnet-online.de) left irc: Ping timeout: 240 seconds
- [08:34] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) left irc: Quit: martincozzi
- [08:42] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) joined #redis.
- [08:49] luckman212_ (~irc@pool-108-41-8-176.nycmny.fios.verizon.net) left irc: Remote host closed the connection
- [08:49] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) left irc: Quit: martincozzi
- [08:50] kenperkins (~textual@50-47-18-37.evrt.wa.frontiernet.net) left irc: Quit: Computer has gone to sleep.
- [08:52] luckman212 (~irc@pool-108-41-8-176.nycmny.fios.verizon.net) joined #redis.
- [08:56] stephank (~stephank@82.197.214.45) joined #redis.
- [09:08] xer0x (~xer0x@static-209-17-135-1.gtcust.grouptelecom.net) joined #redis.
- [09:12] KevBurnsJr (~KevBurnsJ@50.0.103.39) joined #redis.
- [09:14] markdaws (~markdaws@174-24-164-49.tukw.qwest.net) joined #redis.
- [09:16] lux___ (~lux@ppp-159-151.25-151.libero.it) joined #redis.
- [09:17] stask312 (~stask312@212.25.110.130) left irc: Ping timeout: 244 seconds
- [09:18] markdaws (~markdaws@174-24-164-49.tukw.qwest.net) left irc: Read error: Connection reset by peer
- [09:19] markdaws (~markdaws@174-24-164-49.tukw.qwest.net) joined #redis.
- [09:19] rittyan (~rittyan@176.14.223.175) joined #redis.
- [09:22] lux_ (~lux@ppp-159-151.25-151.libero.it) joined #redis.
- [09:22] lux_ -> Guest21933
- [09:23] lux___ (~lux@ppp-159-151.25-151.libero.it) left irc: Read error: Operation timed out
- [09:26] lux___ (~lux@ppp-159-151.25-151.libero.it) joined #redis.
- [09:26] lux___ (~lux@ppp-159-151.25-151.libero.it) left irc: Client Quit
- [09:27] kenperkins (~textual@174-24-164-49.tukw.qwest.net) joined #redis.
- [09:28] lux___ (~lux@ppp-159-151.25-151.libero.it) joined #redis.
- [09:28] Guest21933 (~lux@ppp-159-151.25-151.libero.it) left irc: Ping timeout: 268 seconds
- [09:31] _macro (~Neil@c-71-204-169-22.hsd1.ca.comcast.net) left irc: Quit: Computer has gone to sleep
- [09:33] brianseeders (~BS@108-216-88-132.lightspeed.bcvloh.sbcglobal.net) joined #redis.
- [09:35] Jrz (~jrz@d152222.upc-d.chello.nl) joined #redis.
- [09:37] solaries_ (~solaries@ppp-188-174-0-167.dynamic.mnet-online.de) joined #redis.
- [09:38] thehodge (~thehodge@82.109.33.196) left irc: Remote host closed the connection
- [09:39] thehodge (~thehodge@82.109.33.196) joined #redis.
- [09:41] luckyruby (~luckyruby@125-187.96-97.tampabay.res.rr.com) joined #redis.
- [09:43] thehodge (~thehodge@82.109.33.196) left irc: Ping timeout: 248 seconds
- [09:50] nopz___ (~nopz___@8.14.117.35) left irc: Ping timeout: 240 seconds
- [09:50] deepthawtz (~deepthawt@c-71-202-101-2.hsd1.ca.comcast.net) joined #redis.
- [09:51] wmoss|away -> wmoss
- [09:51] nawt (~nawt@c-50-132-9-148.hsd1.wa.comcast.net) joined #redis.
- [09:52] chrisjones (~chrisjone@ip68-224-245-47.lv.lv.cox.net) joined #redis.
- [09:52] nawt -> Guest52726
- [09:54] nawtnow (~nawt@c-50-132-9-148.hsd1.wa.comcast.net) left irc: Ping timeout: 248 seconds
- [10:03] seppo0010 (~Adium@186.19.19.229) joined #redis.
- [10:04] thehodge (~thehodge@cpc5-seac20-2-0-cust310.7-2.cable.virginmedia.com) joined #redis.
- [10:15] __alex (~alex@g225249111.adsl.alicedsl.de) joined #redis.
- [10:19] chrisjones (~chrisjone@ip68-224-245-47.lv.lv.cox.net) left irc: Quit: Computer has gone to sleep.
- [10:20] solaries4 (~solaries@host-188-174-184-46.customer.m-online.net) joined #redis.
- [10:23] solaries_ (~solaries@ppp-188-174-0-167.dynamic.mnet-online.de) left irc: Ping timeout: 248 seconds
- [10:28] drbobbeaty_ (~drbobbeat@38.98.137.29) joined #redis.
- [10:28] drbobbeaty (~drbobbeat@38.98.137.29) left irc: Read error: Connection reset by peer
- [10:28] drbobbeaty_ -> drbobbeaty
- [10:33] seppo0010 (~Adium@186.19.19.229) left #redis.
- [10:39] chrisjones (~chrisjone@ip68-224-245-47.lv.lv.cox.net) joined #redis.
- [10:40] pietern (~pieter@208.91.1.14) joined #redis.
- [10:40] #redis: mode change '+v pietern' by ChanServ!ChanServ@services.
- [10:43] drbobbeaty_ (~drbobbeat@38.98.137.29) joined #redis.
- [10:43] drbobbeaty (~drbobbeat@38.98.137.29) left irc: Read error: Connection reset by peer
- [10:43] drbobbeaty_ -> drbobbeaty
- [10:45] martincozzi (~martincoz@209.66.114.6) joined #redis.
- [10:46] martincozzi (~martincoz@209.66.114.6) left irc: Client Quit
- [10:47] martincozzi (~martincoz@209.66.114.6) joined #redis.
- [10:49] axl_ (~axl@173-11-52-113-Minnesota.hfc.comcastbusiness.net) left irc: Read error: Connection reset by peer
- [10:49] axl_ (~axl@75-149-152-225-Minnesota.hfc.comcastbusiness.net) joined #redis.
- [10:49] RobWC (~Adium@2001:470:1f05:f2a:152c:25bd:c0ae:67c9) joined #redis.
- [10:50] axl_ (~axl@75-149-152-225-Minnesota.hfc.comcastbusiness.net) left irc: Remote host closed the connection
- [10:57] brianseeders (~BS@108-216-88-132.lightspeed.bcvloh.sbcglobal.net) left irc: Ping timeout: 255 seconds
- [10:58] wmage1 (~wmage@nat-88-212-40-142.antik.sk) joined #redis.
- [10:59] wmage1 (~wmage@nat-88-212-40-142.antik.sk) left irc: Client Quit
- [11:01] alekx (4e61605a@gateway/web/freenode/ip.78.97.96.90) left irc:
- [11:11] lux_ (~lux@ppp-159-151.25-151.libero.it) joined #redis.
- [11:11] lux_ -> Guest6680
- [11:14] lux___ (~lux@ppp-159-151.25-151.libero.it) left irc: Ping timeout: 248 seconds
- [11:24] pharkmillups (~markphill@75.103.3.220) joined #redis.
- [11:30] nawt (~nawt@c-50-132-9-148.hsd1.wa.comcast.net) joined #redis.
- [11:30] nawt -> Guest34291
- [11:32] Guest52726 (~nawt@c-50-132-9-148.hsd1.wa.comcast.net) left irc: Ping timeout: 240 seconds
- [11:32] arek_deepinit (~arek@esposa.patyk.net.pl) joined #redis.
- [11:46] nsalvo (~nsalvo@190.55.32.117) left irc: Quit: leaving
- [11:52] Comandante (~Comandant@200.41.238.50) joined #redis.
- [12:03] xer0x (~xer0x@static-209-17-135-1.gtcust.grouptelecom.net) left irc: Quit: Linkinus - http://linkinus.com
- [12:03] pietern (~pieter@208.91.1.14) left irc: Quit: pietern
- [12:05] napperjabber_ (~napperjab@149.48.161.10) joined #redis.
- [12:08] napperjabber (~napperjab@149.48.161.10) left irc: Ping timeout: 248 seconds
- [12:08] napperjabber_ -> napperjabber
- [12:12] arek_deepinit (~arek@esposa.patyk.net.pl) left irc: Read error: Connection reset by peer
- [12:20] __alex (~alex@g225249111.adsl.alicedsl.de) left irc: Ping timeout: 240 seconds
- [12:21] mcginleyr1 (~mcginleyr@pool-173-49-55-119.phlapa.fios.verizon.net) joined #redis.
- [12:22] drbobbeaty (~drbobbeat@38.98.137.29) left irc: Read error: Connection reset by peer
- [12:22] drbobbeaty (~drbobbeat@38.98.137.29) joined #redis.
- [12:23] <mcginleyr1> Hey all, is there a good link to a page on memory costs for the different data structures in redis. I need to spec out memory requirements for a project
- [12:23] drbobbeaty (~drbobbeat@38.98.137.29) left irc: Read error: Connection reset by peer
- [12:23] drbobbeaty_ (~drbobbeat@38.98.137.29) joined #redis.
- [12:24] steph021 (~steph021@unaffiliated/steph021) left irc: Quit: Leaving
- [12:28] <mcginleyr1> nm i'm an idot
- [12:28] <mcginleyr1> lol
- [12:36] wmoss -> wmoss|away
- [12:45] rurufufuss (~rurufufus@115-64-27-246.static.tpgi.com.au) joined #redis.
- [12:49] soveran (~soveran@186.19.214.247) left irc: Remote host closed the connection
- [12:54] mcginleyr1 (~mcginleyr@pool-173-49-55-119.phlapa.fios.verizon.net) left irc: Quit: mcginleyr1
- [12:57] wmoss|away -> wmoss
- [12:58] pietern (~pieter@208.91.1.14) joined #redis.
- [12:58] #redis: mode change '+v pietern' by ChanServ!ChanServ@services.
- [12:59] drbobbeaty (~drbobbeat@38.98.137.29) joined #redis.
- [12:59] drbobbeaty_ (~drbobbeat@38.98.137.29) left irc: Read error: Connection reset by peer
- [13:00] CoffeeIV (~rgr@dsl093-217-226.aus1.dsl.speakeasy.net) left irc: Read error: Connection reset by peer
- [13:00] Brend (~brend@60-251-59-178.HINET-IP.hinet.net) joined #redis.
- [13:02] elcuervo (~elcuervo@r186-48-242-66.dialup.adsl.anteldata.net.uy) left irc: Ping timeout: 240 seconds
- [13:10] macabre (~macabre@63.133.215.18) left irc: Read error: Operation timed out
- [13:13] napperjabber (~napperjab@149.48.161.10) left irc: Quit: napperjabber
- [13:30] pietern (~pieter@208.91.1.14) left irc: Quit: pietern
- [13:34] pharkmillups (~markphill@75.103.3.220) left irc: Quit: pharkmillups
- [13:34] petercooper (~petercoop@82.144.254.2) joined #redis.
- [13:35] wmoss -> wmoss|away
- [13:43] wmoss|away -> wmoss
- [13:45] kppullin (~kppullin@pdpc/supporter/active/kppullin) left irc: Read error: Connection reset by peer
- [13:47] kppullin (~kppullin@pdpc/supporter/active/kppullin) joined #redis.
- [13:53] elcuervo (~elcuervo@r190-135-27-121.dialup.adsl.anteldata.net.uy) joined #redis.
- [13:58] elcuervo (~elcuervo@r190-135-27-121.dialup.adsl.anteldata.net.uy) left irc: Remote host closed the connection
- [13:59] RobWC (~Adium@2001:470:1f05:f2a:152c:25bd:c0ae:67c9) left irc: Quit: Leaving.
- [14:02] ron (~ron@unaffiliated/ron) left irc: Ping timeout: 253 seconds
- [14:04] ron (~ron@unaffiliated/ron) joined #redis.
- [14:04] Jrz (~jrz@d152222.upc-d.chello.nl) left irc: Quit: Computer has gone to sleep.
- [14:05] soveran (~soveran@186.19.214.247) joined #redis.
- [14:07] luckman212 (~irc@pool-108-41-8-176.nycmny.fios.verizon.net) left irc: Remote host closed the connection
- [14:13] wmoss -> wmoss|away
- [14:14] xemium99 (~Adium@cpe-76-183-128-16.tx.res.rr.com) joined #redis.
- [14:16] Comandante (~Comandant@200.41.238.50) left irc: Remote host closed the connection
- [14:18] Axsuul (~Axsuul@75-140-75-52.dhcp.mtpk.ca.charter.com) joined #redis.
- [14:22] insin (~insin@host86-148-254-166.range86-148.btcentralplus.com) left irc: Ping timeout: 240 seconds
- [14:25] solaries4 (~solaries@host-188-174-184-46.customer.m-online.net) left irc: Ping timeout: 248 seconds
- [14:25] pietern (~pieter@208.91.1.14) joined #redis.
- [14:25] #redis: mode change '+v pietern' by ChanServ!ChanServ@services.
- [14:26] insin (~insin@host86-148-254-166.range86-148.btcentralplus.com) joined #redis.
- [14:31] napperjabber (~napperjab@68.sub-174-255-16.myvzw.com) joined #redis.
- [14:32] adammck (~adammck@206.217.95.186) left irc: Quit: Leaving...
- [14:33] xemium99 (~Adium@cpe-76-183-128-16.tx.res.rr.com) left irc: Quit: Leaving.
- [14:43] brianseeders (~BS@108-216-88-132.lightspeed.bcvloh.sbcglobal.net) joined #redis.
- [14:43] pranq (pranq@unaffiliated/contempt) left irc: Ping timeout: 268 seconds
- [14:44] pranq (pranq@unaffiliated/contempt) joined #redis.
- [14:45] wmoss|away -> wmoss
- [14:50] wmoss -> wmoss|away
- [14:52] soveran (~soveran@186.19.214.247) left irc: Remote host closed the connection
- [15:01] wmoss|away -> wmoss
- [15:02] wilmoore_ (~wilmoore@c-67-190-17-108.hsd1.co.comcast.net) joined #redis.
- [15:02] wilmoore (~wilmoore@c-67-190-17-108.hsd1.co.comcast.net) left irc: Read error: Connection reset by peer
- [15:06] jonesy (~jonesy@68.64.144.221) left irc: Quit: Computer has gone to sleep.
- [15:13] anydot (~anydot@oratica.redrum.cz) joined #redis.
- [15:17] Comandante (~Comandant@68-178-114-200.fibertel.com.ar) joined #redis.
- [15:18] jrydberg_ (~jrydberg@81-235-188-3-no48.tbcn.telia.com) left irc: Quit: This computer has gone to sleep
- [15:21] Comandante (~Comandant@68-178-114-200.fibertel.com.ar) left irc: Remote host closed the connection
- [15:25] tilgovi (~randall@couchdb/developer/tilgovi) joined #redis.
- [15:28] drbobbeaty (~drbobbeat@38.98.137.29) left irc: Quit: drbobbeaty
- [15:37] nu7hatch_ (~cubox@r186-48-242-66.dialup.adsl.anteldata.net.uy) joined #redis.
- [15:41] nu7hatch (~cubox@r186-48-237-57.dialup.adsl.anteldata.net.uy) left irc: Ping timeout: 240 seconds
- [15:41] nu7hatch_ -> nu7hatch
- [15:56] wilmoore_ (~wilmoore@c-67-190-17-108.hsd1.co.comcast.net) left irc: Remote host closed the connection
- [15:58] wilmoore (~wilmoore@c-67-190-17-108.hsd1.co.comcast.net) joined #redis.
- [15:58] rittyan (~rittyan@176.14.223.175) left irc: Remote host closed the connection
- [16:01] nu7hatch_ (~cubox@r186-48-249-89.dialup.adsl.anteldata.net.uy) joined #redis.
- [16:04] iFire (~swirls@unaffiliated/ifire) left irc:
- [16:04] iFire (~swirls@unaffiliated/ifire) joined #redis.
- [16:04] nu7hatch (~cubox@r186-48-242-66.dialup.adsl.anteldata.net.uy) left irc: Ping timeout: 240 seconds
- [16:04] nu7hatch_ -> nu7hatch
- [16:07] thehodge (~thehodge@cpc5-seac20-2-0-cust310.7-2.cable.virginmedia.com) left irc: Remote host closed the connection
- [16:07] thehodge (~thehodge@2001:470:1f09:13a3:558a:2106:eaee:ca1e) joined #redis.
- [16:12] thehodge (~thehodge@2001:470:1f09:13a3:558a:2106:eaee:ca1e) left irc: Ping timeout: 252 seconds
- [16:30] Sarevok (~locke@rrcs-98-101-176-143.midsouth.biz.rr.com) left #redis.
- [16:31] xjiujiu (~quassel@218.77.14.195) joined #redis.
- [16:37] stephank (~stephank@82.197.214.45) left irc: Quit: *Poof!*
- [16:37] jrydberg_ (~jrydberg@81-235-188-3-no48.tbcn.telia.com) joined #redis.
- [16:46] jrydberg_ (~jrydberg@81-235-188-3-no48.tbcn.telia.com) left irc: Quit: This computer has gone to sleep
- [16:49] xjiujiu (~quassel@218.77.14.195) left irc: Read error: Connection reset by peer
- [16:52] thehodge (~thehodge@2001:470:1f09:13a3:54d4:f3a7:fe32:abaf) joined #redis.
- [16:53] QiBol (~QiBol@nodester.com) left irc: K-Lined
- [16:59] X99 (~quassel@218.77.14.195) joined #redis.
- [17:03] TimTimTim (TimTim@cpe-098-026-149-108.triad.res.rr.com) left irc: Ping timeout: 240 seconds
- [17:15] martincozzi (~martincoz@209.66.114.6) left irc: Quit: martincozzi
- [17:15] napperjabber (~napperjab@68.sub-174-255-16.myvzw.com) left irc: Read error: Connection reset by peer
- [17:15] napperjabber (~napperjab@68.sub-174-255-16.myvzw.com) joined #redis.
- [17:18] napperjabber (~napperjab@68.sub-174-255-16.myvzw.com) left irc: Client Quit
- [17:20] awksed3greep (~awksedgre@c-24-98-243-58.hsd1.ga.comcast.net) joined #redis.
- [17:21] awksedgreep (~awksedgre@c-24-98-243-58.hsd1.ga.comcast.net) left irc: Ping timeout: 244 seconds
- [17:21] awksed2greep (~awksedgre@c-24-98-243-58.hsd1.ga.comcast.net) left irc: Ping timeout: 244 seconds
- [17:22] nicholasf (~nicholasf@ppp196-159.static.internode.on.net) joined #redis.
- [17:29] Guest6680 (~lux@ppp-159-151.25-151.libero.it) left irc: Quit: This computer has gone to sleep
- [17:32] thehodge (~thehodge@2001:470:1f09:13a3:54d4:f3a7:fe32:abaf) left irc: Remote host closed the connection
- [17:32] thehodge (~thehodge@cpc5-seac20-2-0-cust310.7-2.cable.virginmedia.com) joined #redis.
- [17:36] thehodge (~thehodge@cpc5-seac20-2-0-cust310.7-2.cable.virginmedia.com) left irc: Ping timeout: 240 seconds
- [17:38] d0k (~d0k@p5B3B1342.dip.t-dialin.net) left irc: Quit: This sleep has gone computing.
- [17:52] TimTimTim (TimTim@cpe-098-026-149-108.triad.res.rr.com) joined #redis.
- [17:52] Axsuul (~Axsuul@75-140-75-52.dhcp.mtpk.ca.charter.com) left irc: Read error: Connection reset by peer
- [17:53] kenperkins (~textual@174-24-164-49.tukw.qwest.net) left irc: Ping timeout: 268 seconds
- [17:55] ncode (~ncode@189.38.154.97) joined #redis.
- [17:55] ncode (~ncode@189.38.154.97) left irc: Changing host
- [17:55] ncode (~ncode@unaffiliated/ncode) joined #redis.
- [17:56] Axsuul (~Axsuul@75-140-75-52.dhcp.mtpk.ca.charter.com) joined #redis.
- [18:06] awksedgreep (~awksedgre@c-24-98-243-58.hsd1.ga.comcast.net) joined #redis.
- [18:06] markdaws (~markdaws@174-24-164-49.tukw.qwest.net) left irc: Remote host closed the connection
- [18:06] awksedgreep (~awksedgre@c-24-98-243-58.hsd1.ga.comcast.net) left irc: Remote host closed the connection
- [18:20] _macro (~Neil@c-71-204-169-22.hsd1.ca.comcast.net) joined #redis.
- [18:26] chrisjones (~chrisjone@ip68-224-245-47.lv.lv.cox.net) left irc: Quit: Textual IRC Client: http://www.textualapp.com/
- [18:30] wmoss -> wmoss|away
- [18:30] _macro (~Neil@c-71-204-169-22.hsd1.ca.comcast.net) left irc: Quit: Computer has gone to sleep
- [18:57] KevBurnsJr (~KevBurnsJ@50.0.103.39) left irc:
- [19:01] _macro (~Neil@c-71-204-169-22.hsd1.ca.comcast.net) joined #redis.
- [19:06] arek_deepinit (~arek@esposa.patyk.net.pl) joined #redis.
- [19:08] rurufufuss (~rurufufus@115-64-27-246.static.tpgi.com.au) left irc: Read error: Connection reset by peer
- [19:12] petercooper (~petercoop@82.144.254.2) left irc: Remote host closed the connection
- [19:13] petercooper (~petercoop@82.144.254.2) joined #redis.
- [19:27] jonesy (~jonesy@pool-173-71-115-162.cmdnnj.fios.verizon.net) joined #redis.
- [19:32] tilgovi (~randall@couchdb/developer/tilgovi) left irc: Ping timeout: 240 seconds
- [19:36] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) joined #redis.
- [19:36] macabre (~macabre@cpe-66-69-218-227.austin.res.rr.com) joined #redis.
- [19:39] _macro (~Neil@c-71-204-169-22.hsd1.ca.comcast.net) left irc: Quit: Computer has gone to sleep
- [19:44] alc (~nek@61.135.165.159) joined #redis.
- [19:48] soveran (~soveran@186.19.214.247) joined #redis.
- [19:50] tilgovi (~randall@ool-4357ca60.dyn.optonline.net) joined #redis.
- [19:50] tilgovi (~randall@ool-4357ca60.dyn.optonline.net) left irc: Changing host
- [19:50] tilgovi (~randall@couchdb/developer/tilgovi) joined #redis.
- [19:52] alc (~nek@61.135.165.159) left irc: Remote host closed the connection
- [19:54] pietern (~pieter@208.91.1.14) left irc: Quit: pietern
- [19:55] tjholowaychuk (~tjholoway@S010658b03565e6c6.gv.shawcable.net) left irc: Quit: Bye!
- [20:01] deepthawtz (~deepthawt@c-71-202-101-2.hsd1.ca.comcast.net) left irc: Quit: Leaving...
- [20:02] deepthawtz (~deepthawt@c-71-202-101-2.hsd1.ca.comcast.net) joined #redis.
- [20:02] kushal (~kdas@fedora/kushal) joined #redis.
- [20:03] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) left irc: Quit: martincozzi
- [20:09] agentzh (~agentz@nginx/adept/agentzh) joined #redis.
- [20:10] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) joined #redis.
- [20:11] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) left irc: Client Quit
- [20:11] kushal (~kdas@fedora/kushal) left irc: Ping timeout: 240 seconds
- [20:19] macabre (~macabre@cpe-66-69-218-227.austin.res.rr.com) left irc: Remote host closed the connection
- [20:25] kushal (~kdas@fedora/kushal) joined #redis.
- [20:31] soveran (~soveran@186.19.214.247) left irc: Remote host closed the connection
- [20:31] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) joined #redis.
- [20:36] verandor (1f138027@gateway/web/freenode/ip.31.19.128.39) joined #redis.
- [20:38] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) left irc: Quit: martincozzi
- [20:42] S2kx (~S1kx@ip-95-223-80-198.unitymediagroup.de) left irc: Read error: Connection reset by peer
- [20:42] S1kx (~S1kx@pdpc/supporter/monthlybyte/s1kx) joined #redis.
- [20:43] <verandor> hello.. has someone experience with redis+php+greatTextValues? it seems that the insert rate drops if the value is greater than (round about) 8000 bytes.. is someone else facing this problem?
- [20:49] _macro (~Neil@c-71-204-169-22.hsd1.ca.comcast.net) joined #redis.
- [20:49] arek_deepinit (~arek@esposa.patyk.net.pl) left irc: Ping timeout: 240 seconds
- [20:50] ncode (~ncode@unaffiliated/ncode) left irc: Quit: Computer has gone to sleep.
- [20:59] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) joined #redis.
- [21:01] martincozzi (~martincoz@c-67-180-194-70.hsd1.ca.comcast.net) left irc: Client Quit
- [21:02] kenperkins (~textual@50-47-18-37.evrt.wa.frontiernet.net) joined #redis.
- [21:19] soveran (~soveran@186.19.214.247) joined #redis.
- [21:21] verandor (1f138027@gateway/web/freenode/ip.31.19.128.39) left irc: Quit: Page closed
- [21:21] brianseeders (~BS@108-216-88-132.lightspeed.bcvloh.sbcglobal.net) left irc: Ping timeout: 240 seconds
- [21:25] soveran (~soveran@186.19.214.247) left irc: Remote host closed the connection
- [21:34] chakrit (~chakrit@ppp-115-87-237-118.revip4.asianet.co.th) joined #redis.
- [21:35] johnsanders (~johnsande@209.66.114.6) left irc: Quit: Linkinus - http://linkinus.com
- [21:52] insin (~insin@host86-148-254-166.range86-148.btcentralplus.com) left irc: Quit: What's the point in giving us haaaaannnds?
- [22:18] NuckOff -> Nuck
- [22:22] stask312 (~stask312@62.219.149.27) joined #redis.
- [22:44] TimTimTim (TimTim@cpe-098-026-149-108.triad.res.rr.com) left irc: Ping timeout: 240 seconds
- [23:10] RobWC (~Adium@2001:470:1f05:f2a:594c:8e26:ae37:7e4) joined #redis.
- [23:11] RobWC (~Adium@2001:470:1f05:f2a:594c:8e26:ae37:7e4) left irc: Client Quit
- [23:22] horsey_ (~horsey@203.92.58.165) joined #redis.
- [23:23] nicholas_ (~nicholasf@ppp196-159.static.internode.on.net) joined #redis.
- [23:25] horsey (~horsey@27.34.244.74) left irc: Ping timeout: 276 seconds
- [23:27] nicholasf (~nicholasf@ppp196-159.static.internode.on.net) left irc: Ping timeout: 252 seconds
- [23:27] nicholasf (~nicholasf@ppp196-159.static.internode.on.net) joined #redis.
- [23:30] wilmoore (~wilmoore@c-67-190-17-108.hsd1.co.comcast.net) left irc: Remote host closed the connection
- [23:31] nicholas_ (~nicholasf@ppp196-159.static.internode.on.net) left irc: Ping timeout: 276 seconds
- [23:31] wilmoore (~wilmoore@c-67-190-17-108.hsd1.co.comcast.net) joined #redis.
- [23:35] solaries1 (~solaries@ppp-93-104-166-129.dynamic.mnet-online.de) joined #redis.
- [23:36] X99 (~quassel@218.77.14.195) left irc: Read error: Connection reset by peer
- [23:40] Jrz (~jrz@d152222.upc-d.chello.nl) joined #redis.
- [23:45] __alex (~alex@g231176203.adsl.alicedsl.de) joined #redis.
- [23:52] NetRoY (~NetRoY@nat/yahoo/x-crvbiucqusojbzma) joined #redis.
- [23:52] nicholasf (~nicholasf@ppp196-159.static.internode.on.net) left irc: Remote host closed the connection
- [23:53] nicholasf (~nicholasf@ppp196-159.static.internode.on.net) joined #redis.
- [23:56] Jrz (~jrz@d152222.upc-d.chello.nl) left irc: Quit: Computer has gone to sleep.
- [00:00] --- Fri Dec 23 2011