Permalink
Browse files

init commit

  • Loading branch information...
0 parents commit f655dfa46e5e5e040bda5f449539b140fc5886a6 Blake Mizerany committed Mar 5, 2010
Showing with 406 additions and 0 deletions.
  1. +3 −0 .gitignore
  2. +11 −0 ebin/redis.app
  3. +232 −0 redis.conf
  4. +118 −0 src/redis.erl
  5. +4 −0 start
  6. +37 −0 t/001_redis_slurp_test.t
  7. +1 −0 test
@@ -0,0 +1,3 @@
+*.rdb
+*.beam
+*.dump
@@ -0,0 +1,11 @@
+{
+ application,
+ redis,
+ [
+ {description, "hot shit!"},
+ {vsn, "1.0.0"},
+ {modules, [redis]},
+ {applications, [stdlib, kernel]},
+ {registered, [redis]}
+ ]
+}.
@@ -0,0 +1,232 @@
+# Redis configuration file example
+
+# By default Redis does not run as a daemon. Use 'yes' if you need it.
+# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
+daemonize no
+
+# When run as a daemon, Redis write a pid file in /var/run/redis.pid by default.
+# You can specify a custom pid file location here.
+pidfile /var/run/redis.pid
+
+# Accept connections on the specified port, default is 6379
+port 6660
+
+# If you want you can bind a single interface, if the bind option is not
+# specified all the interfaces will listen for connections.
+#
+# bind 127.0.0.1
+
+# Close the connection after a client is idle for N seconds (0 to disable)
+timeout 300
+
+# Set server verbosity to 'debug'
+# it can be one of:
+# debug (a lot of information, useful for development/testing)
+# notice (moderately verbose, what you want in production probably)
+# warning (only very important / critical messages are logged)
+loglevel debug
+
+# Specify the log file name. Also 'stdout' can be used to force
+# the demon to log on the standard output. Note that if you use standard
+# output for logging but daemonize, logs will be sent to /dev/null
+logfile stdout
+
+# Set the number of databases. The default database is DB 0, you can select
+# a different one on a per-connection basis using SELECT <dbid> where
+# dbid is a number between 0 and 'databases'-1
+databases 10
+
+################################ SNAPSHOTTING #################################
+#
+# Save the DB on disk:
+#
+# save <seconds> <changes>
+#
+# Will save the DB if both the given number of seconds and the given
+# number of write operations against the DB occurred.
+#
+# In the example below the behaviour will be to save:
+# after 900 sec (15 min) if at least 1 key changed
+# after 300 sec (5 min) if at least 10 keys changed
+# after 60 sec if at least 10000 keys changed
+#
+# Note: you can disable saving at all commenting all the "save" lines.
+
+#save 900 1
+#save 300 10
+#save 60 10000
+
+# Compress string objects using LZF when dump .rdb databases?
+# For default that's set to 'yes' as it's almost always a win.
+# If you want to save some CPU in the saving child set it to 'no' but
+# the dataset will likely be bigger if you have compressible values or keys.
+rdbcompression yes
+
+# The filename where to dump the DB
+dbfilename dump.rdb
+
+# For default save/load DB in/from the working directory
+# Note that you must specify a directory not a file name.
+dir ./
+
+################################# REPLICATION #################################
+
+# Master-Slave replication. Use slaveof to make a Redis instance a copy of
+# another Redis server. Note that the configuration is local to the slave
+# so for example it is possible to configure the slave to save the DB with a
+# different interval, or to listen to another port, and so on.
+#
+# slaveof <masterip> <masterport>
+
+# If the master is password protected (using the "requirepass" configuration
+# directive below) it is possible to tell the slave to authenticate before
+# starting the replication synchronization process, otherwise the master will
+# refuse the slave request.
+#
+# masterauth <master-password>
+
+################################## SECURITY ###################################
+
+# Require clients to issue AUTH <PASSWORD> before processing any other
+# commands. This might be useful in environments in which you do not trust
+# others with access to the host running redis-server.
+#
+# This should stay commented out for backward compatibility and because most
+# people do not need auth (e.g. they run their own servers).
+#
+# requirepass foobared
+
+################################### LIMITS ####################################
+
+# Set the max number of connected clients at the same time. By default there
+# is no limit, and it's up to the number of file descriptors the Redis process
+# is able to open. The special value '0' means no limts.
+# Once the limit is reached Redis will close all the new connections sending
+# an error 'max number of clients reached'.
+#
+# maxclients 128
+
+# Don't use more memory than the specified amount of bytes.
+# When the memory limit is reached Redis will try to remove keys with an
+# EXPIRE set. It will try to start freeing keys that are going to expire
+# in little time and preserve keys with a longer time to live.
+# Redis will also try to remove objects from free lists if possible.
+#
+# If all this fails, Redis will start to reply with errors to commands
+# that will use more memory, like SET, LPUSH, and so on, and will continue
+# to reply to most read-only commands like GET.
+#
+# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
+# 'state' server or cache, not as a real DB. When Redis is used as a real
+# database the memory usage will grow over the weeks, it will be obvious if
+# it is going to use too much memory in the long run, and you'll have the time
+# to upgrade. With maxmemory after the limit is reached you'll start to get
+# errors for write operations, and this may even lead to DB inconsistency.
+#
+# maxmemory <bytes>
+
+############################## APPEND ONLY MODE ###############################
+
+# By default Redis asynchronously dumps the dataset on disk. If you can live
+# with the idea that the latest records will be lost if something like a crash
+# happens this is the preferred way to run Redis. If instead you care a lot
+# about your data and don't want to that a single record can get lost you should
+# enable the append only mode: when this mode is enabled Redis will append
+# every write operation received in the file appendonly.log. This file will
+# be read on startup in order to rebuild the full dataset in memory.
+#
+# Note that you can have both the async dumps and the append only file if you
+# like (you have to comment the "save" statements above to disable the dumps).
+# Still if append only mode is enabled Redis will load the data from the
+# log file at startup ignoring the dump.rdb file.
+#
+# The name of the append only file is "appendonly.log"
+#
+# IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
+# log file in background when it gets too big.
+
+appendonly no
+
+# The fsync() call tells the Operating System to actually write data on disk
+# instead to wait for more data in the output buffer. Some OS will really flush
+# data on disk, some other OS will just try to do it ASAP.
+#
+# Redis supports three different modes:
+#
+# no: don't fsync, just let the OS flush the data when it wants. Faster.
+# always: fsync after every write to the append only log . Slow, Safest.
+# everysec: fsync only if one second passed since the last fsync. Compromise.
+#
+# The default is "always" that's the safer of the options. It's up to you to
+# understand if you can relax this to "everysec" that will fsync every second
+# or to "no" that will let the operating system flush the output buffer when
+# it want, for better performances (but if you can live with the idea of
+# some data loss consider the default persistence mode that's snapshotting).
+
+appendfsync always
+# appendfsync everysec
+# appendfsync no
+
+################################ VIRTUAL MEMORY ###############################
+
+# Virtual Memory allows Redis to work with datasets bigger than the actual
+# amount of RAM needed to hold the whole dataset in memory.
+# In order to do so very used keys are taken in memory while the other keys
+# are swapped into a swap file, similarly to what operating systems do
+# with memory pages.
+#
+# To enable VM just set 'vm-enabled' to yes, and set the following three
+# VM parameters accordingly to your needs.
+
+# vm-enabled yes
+vm-enabled no
+
+# vm-max-memory configures the VM to use at max the specified amount of
+# RAM. Everything that deos not fit will be swapped on disk *if* possible, that
+# is, if there is still enough contiguous space in the swap file.
+vm-max-memory 10000000
+
+# Redis swap files is split into pages. An object can be saved using multiple
+# contiguous pages, but pages can't be shared between different objects.
+# So if your page is too big, small objects swapped out on disk will waste
+# a lot of space. If you page is too small, there is less space in the swap
+# file (assuming you configured the same number of total swap file pages).
+#
+# If you use a lot of small objects, use a page size of 64 or 32 bytes.
+# If you use a lot of big objects, use a bigger page size.
+# If unsure, use the defualt :)
+vm-page-size 256
+
+# Number of total memory pages in the swap file.
+# Given that the page table (a bitmap of free/used pages) is taken in memory,
+# every 8 pages on disk will consume 1 byte of RAM.
+#
+# The total swap size is vm-page-size * vm-pages
+#
+# With the default of 256-bytes memory pages and 104857600 pages Redis will
+# use a 25 GB swap file, that will use rougly 13 MB of RAM for the page table.
+vm-pages 104857600
+
+############################### ADVANCED CONFIG ###############################
+
+# Glue small output buffers together in order to send small replies in a
+# single TCP packet. Uses a bit more CPU but most of the times it is a win
+# in terms of number of queries per second. Use 'yes' if unsure.
+glueoutputbuf yes
+
+# Use object sharing. Can save a lot of memory if you have many common
+# string in your dataset, but performs lookups against the shared objects
+# pool so it uses more CPU and can be a bit slower. Usually it's a good
+# idea.
+#
+# When object sharing is enabled (shareobjects yes) you can use
+# shareobjectspoolsize to control the size of the pool used in order to try
+# object sharing. A bigger pool size will lead to better sharing capabilities.
+# In general you want this value to be at least the double of the number of
+# very common strings you have in your dataset.
+#
+# WARNING: object sharing is experimental, don't enable this feature
+# in production before of Redis 1.0-stable. Still please try this feature in
+# your development environment so that we can test it better.
+shareobjects no
+shareobjectspoolsize 1024
@@ -0,0 +1,118 @@
+-module(redis).
+-behaviour(gen_server).
+
+%% gen_server exports
+-export([
+ init/1,
+ handle_call/3, handle_cast/2, handle_info/2,
+ terminate/2, code_change/3
+]).
+
+-export([
+ connect/2,
+ q/1
+]).
+
+-define(NL, "\r\n").
+
+%% ----------
+%% Publi API
+%% ----------
+
+connect(Ip, Port) ->
+ Result = gen_server:start_link({local, ?MODULE}, ?MODULE, {Ip, Port}, []),
+ case Result of
+ {ok, _Pid} ->
+ ok;
+ Error ->
+ Error
+ end.
+
+q(Parts) ->
+ gen_server:call(?MODULE, {request, Parts}).
+
+%% Private API
+
+strip(B) when is_binary(B) ->
+ S = size(B) - 2,
+ <<B1:S/binary, _/binary>> = B,
+ B1.
+
+read_resp(Socket) ->
+ inet:setopts(Socket, [{packet, line}]),
+ {ok, Line} = gen_tcp:recv(Socket, 0),
+ case Line of
+ <<"*", Rest/binary>> ->
+ Count = list_to_integer(binary_to_list(strip(Rest))),
+ read_multi_bulk(Socket, Count, []);
+ <<"+", Rest/binary>> ->
+ {ok, strip(Rest)};
+ <<"-", Rest/binary>> ->
+ {error, strip(Rest)};
+ <<":", Size/binary>> ->
+ {ok, list_to_integer(binary_to_list(strip(Size)))};
+ <<"$", Size/binary>> ->
+ Size1 = list_to_integer(binary_to_list(strip(Size))),
+ read_body(Socket, Size1);
+ <<"\r\n">> ->
+ read_resp(Socket);
+ Uknown ->
+ {unknown, Uknown}
+ end.
+
+read_body(_Socket, -1) ->
+ {ok, null};
+read_body(Socket, Size) ->
+ inet:setopts(Socket, [{packet, raw}]),
+ gen_tcp:recv(Socket, Size).
+
+read_multi_bulk(_Data, 0, Acc) ->
+ lists:reverse(Acc);
+read_multi_bulk(Socket, Count, Acc) ->
+ Acc1 = [read_resp(Socket) | Acc],
+ read_multi_bulk(Socket, Count-1, Acc1).
+
+build_request(Args) when is_list(Args) ->
+ Count = length(Args),
+ F = fun(V) -> ["$", to_part(length(to_part(V))), ?NL, to_part(V), ?NL] end,
+ Args1 = lists:map(F, Args),
+ ["*", to_part(Count), ?NL, Args1, ?NL].
+
+to_part(A) when is_atom(A) ->
+ string:to_upper(atom_to_list(A));
+to_part(B) when is_binary(B) ->
+ binary_to_list(B);
+to_part(I) when is_integer(I) ->
+ integer_to_list(I);
+to_part(L) when is_list(L) ->
+ L.
+
+
+%% ----------
+%% gen_server
+%% ----------
+
+init({Ip, Port}) ->
+ SocketOpts = [binary, {packet, line}, {active, false}, {recbuf, 1024}],
+ Result = gen_tcp:connect(Ip, Port, SocketOpts),
+ case Result of
+ {ok, Socket} ->
+ {ok, Socket};
+ Error ->
+ {stop, Error}
+ end.
+
+handle_call({request, Parts}, _From, Socket) ->
+ ToSend = build_request(Parts),
+ Result = case gen_tcp:send(Socket, ToSend) of
+ ok ->
+ read_resp(Socket);
+ Error ->
+ Error
+ end,
+ {reply, Result, Socket}.
+
+handle_cast(_, _) -> ok.
+handle_info(_, _) -> ok.
+terminate(_, _) -> ok.
+code_change(_, _, _) -> ok.
4 start
@@ -0,0 +1,4 @@
+#!/bin/sh
+set -e
+rebar compile
+erl -pa ebin/ -boot start_sasl -eval 'redis:connect("127.0.0.1", 6660)'
Oops, something went wrong.

0 comments on commit f655dfa

Please sign in to comment.