On Thursday, October 11, 2012, Marc Gravell wrote:
> Further, if I add a separate wait after *every* operation (i.e. we
> completely fail to use the pipeline), then it **still** only takes about
> 100ms. You can simulate this by the addition of a Wait in the loop:
> for (int i = 0; i < 1000; ++i)
> {
> string key = "aaaaaaaaaaa" + i;
> string value = "bbbbbbbbbb";
> last = redis_client.Strings.Set(0, key, value);
> redis_client.Wait(last);
> }
> So: I don't know what Sider is doing for the rest of the time, but it
> isn't a redis-server issue.
> Marc
> On 11 October 2012 12:19, Marc Gravell <marc.grav...@gmail.com> wrote:
> This looks like a problem with that client; I have the following 2 tests,
> one using BookSleeve, one using Sider. The first (BookSleeve) takes 3ms,
> the second (Sider) takes 2391ms. If I don't pause to wait for the replies,
> BookSleeve takes 1ms:
> [Test]
> public void TestBookSleevePipelinePerformance()
> {
> using (var redis_client = new
> BookSleeve.RedisConnection("localhost", 6379))
> {
> redis_client.Open();
> var watch = Stopwatch.StartNew();
> Task last = null;
> for (int i = 0; i < 1000; ++i)
> {
> string key = "aaaaaaaaaaa" + i;
> string value = "bbbbbbbbbb";
> last = redis_client.Strings.Set(0, key, value);
> }
> // not required, but for the fun, wait until we've
> // had all of the replies
> redis_client.Wait(last);
> watch.Stop();
> Console.WriteLine("{0}ms", watch.ElapsedMilliseconds);
> }
> }
> [Test]
> public void TestSiderPipelinePerformance()
> {
> using (var redis_client = new Sider.RedisClient("localhost",
> 6379))
> {
> var watch = Stopwatch.StartNew();
> redis_client.Pipeline(c =>
> {
> for (int i = 0; i < 1000; ++i)
> {
> string key = "aaaaaaaaaaa" + i;
> string value = "bbbbbbbbbb";
> c.Set(key, value);
> }
> });
> watch.Stop();
> Console.WriteLine("{0}ms", watch.ElapsedMilliseconds);
> }
> }
> On 11 October 2012 12:11, Didier Spezia <didier...@gmail.com> wrote:
> >> .*Official benchmark page <http://redis.io/topics/benchmarks>* of
> Redis says about possibility of ~100000 SET operations per second. I have
> less then 1000... What's the problem?
> I would suggest to try the benchmark program by yourself: it is trivial to
> launch
> and part of the Redis distribution. So you will be able to check if the
> problem is
> on server side or client side.
> Regards,
> Didier.
> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/redis-db/-/E9ezx7ziAxcJ.
> To post to this group, send email to redis-db@googlegroups.com.
> To unsubscribe from this group, send email to
> redis-db+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/redis-db?hl=en.
> --
> Regards,
> Marc
> --
> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To post to this group, send email to redis-db@googlegroups.com<javascript:_e({}, 'cvml', 'redis-db@googlegroups.com');>
> .
> To unsubscribe from this group, send email to
> redis-db+unsubscribe@googlegroups.com <javascript:_e({}, 'cvml',
> 'redis-db%2Bunsubscribe@googlegroups.com');>.
> For more options, visit this group at
> http://groups.google.com/group/redis-db?hl=en.
