http://streamhacker.com/2009/05/20/building-a-nltk-freqdist-on-redis/#utm_source=feed&utm_medium=feed&utm_campaign=feed Weotta be Hacking Thu, 08 Jul 2010 07:41:51 +0000 hourly 1 http://wordpress.org/?v=3.0 http://streamhacker.com/2009/05/20/building-a-nltk-freqdist-on-redis/comment-page-1/#comment-28 Jacob Sun, 24 May 2009 02:59:51 +0000 http://streamhacker.wordpress.com/?p=251#comment-28 I have, but I didn't see any way to do sliceable lists. I see that I could concat string values together, but then what? Get the whole string, split it, and return a small slice? That's what I was doing in BerkeleyDB, and it's incredibly inefficient with large lists. I have, but I didn’t see any way to do sliceable lists. I see that I could concat string values together, but then what? Get the whole string, split it, and return a small slice? That’s what I was doing in BerkeleyDB, and it’s incredibly inefficient with large lists.

]]> http://streamhacker.com/2009/05/20/building-a-nltk-freqdist-on-redis/comment-page-1/#comment-27 casey Sun, 24 May 2009 02:47:06 +0000 http://streamhacker.wordpress.com/?p=251#comment-27 have you looked at tokyo tyrant? It meets your requirements, and is a lot more mature than redis. have you looked at tokyo tyrant? It meets your requirements, and is a lot more mature than redis.

]]>