pub-expires benchmark for Redis 2.6 (branch at https://github.com/kroepke/redis/tree/2.6-expire-pubsub ) run on Intel(R) Xeon(R) CPU E5430 @ 2.66GHz, 2 CPUs, 4 cores each. 32GB RAM

gistfile1.txt

Server started with:
./src/redis-server --save "" # to disable background saves

with CONFIG SET pub-expires "no"

test-4.experimental.fra2:~/redis # for i in 1 2 3; do ./src/redis-benchmark -r 10000000 -t setex -e 1 -n 1000000 --csv ; done
"SET","54424.73"
"SET","52988.55"
"SET","53853.20"

with CONFIG SET pub-expires "yes"
no subscribers on channel "expired"

test-4.experimental.fra2:~/redis # for i in 1 2 3; do ./src/redis-benchmark -r 10000000 -t setex -e 1 -n 1000000 --csv ; done
"SET","54162.38"
"SET","53364.64"
"SET","53648.07"

with CONFIG SET pub-expires "yes"
one subscriber with: ./src/redis-cli subscribe "expired" > /dev/null

test-4.experimental.fra2:~/redis # for i in 1 2 3; do ./src/redis-benchmark -r 10000000 -t setex -e 1 -n 1000000 --csv ; done
"SET","55500.05"
"SET","52064.35"
"SET","52254.80"

with CONFIG SET pub-expires "yes"
and 3 subscribers:
./src/redis-cli subscribe "expired" > /dev/null &
./src/redis-cli subscribe "expired" > /dev/null &
./src/redis-cli subscribe "expired" > /dev/null &

test-4.experimental.fra2:~/redis # for i in 1 2 3; do ./src/redis-benchmark -r 10000000 -t setex -e 1 -n 1000000 --csv ; done
"SET","50712.51"
"SET","46613.53"
"SET","46999.11"