On Sun, Feb 17, 2013 at 2:30 PM, Erdem Agaoglu <erdem.agaoglu@xxxxxxxxx> wrote: > Hi Yehuda, > > Thanks for fast reply. > We are running 0.56.3. On ubuntu 12.04. > > I disabled ops log using > 'rgw enable ops log = false' > but i missed 'debug rgw = 0' so what i did was simply 'log file = /dev/null' > :) > > Anyways. i tried 'debug rgw = 0' but it didn't change anything. To see > what's going on in rgw i did 'debug rgw=2' and rerun the test. > > # cat radosgw.log |grep put_obj |grep status=200 > ... > 2013-02-17 13:51:37.415981 7f54167f4700 2 req 613:0.327243:s3:PUT > /mybucket/benchmark_data_ceph-10_31019_object611:put_obj:http status=200 > 2013-02-17 13:51:37.431779 7f54137ee700 2 req 614:0.318996:s3:PUT > /mybucket/benchmark_data_ceph-10_31019_object612:put_obj:http status=200 > 2013-02-17 13:51:37.447688 7f53f37ae700 2 req 615:0.319085:s3:PUT > /mybucket/benchmark_data_ceph-10_31019_object613:put_obj:http status=200 > 2013-02-17 13:51:37.460531 7f53fbfbf700 2 req 581:0.887859:s3:PUT > /mybucket/benchmark_data_ceph-10_31019_object579:put_obj:http status=200 > 2013-02-17 13:51:37.468215 7f5411feb700 2 req 616:0.326575:s3:PUT > /mybucket/benchmark_data_ceph-10_31019_object614:put_obj:http status=200 > 2013-02-17 13:51:37.480233 7f54267fc700 2 req 617:0.335292:s3:PUT > /mybucket/benchmark_data_ceph-10_31019_object615:put_obj:http status=200 > 2013-02-17 13:51:37.503042 7f54147f0700 2 req 618:0.330277:s3:PUT > /mybucket/benchmark_data_ceph-10_31019_object616:put_obj:http status=200 > 2013-02-17 13:51:37.519647 7f5413fef700 2 req 619:0.306762:s3:PUT > /mybucket/benchmark_data_ceph-10_31019_object617:put_obj:http status=200 > 2013-02-17 13:51:37.520274 7f5427fff700 2 req 620:0.307374:s3:PUT > /mybucket/benchmark_data_ceph-10_31019_object618:put_obj:http status=200 > ... > > If i read this correctly requests take 0.32 secs on average. Again, if i'm > looking at things the right way, that would make 320 secs for like 1175 > requests, and if i divide that by 20 paralel requests that would give 18.8 > secs, which means for a 20 sec test most of the time is passed at radosgw > <-> rados. It would be interesting looking at the messenger log (debug ms = 1) and correlate it with the rgw log (debug rgw = 20). You'll need to look at a specific request that's slow and filter by the thread id (the hex number in the 3rd column). It'll contain most of the interesting stuff, except for the response messages. > > i'm not sure how to check apache <-> radosgw or if that's relevant. But i > can say there is no problem between rest-client <-> apache as i am getting > the same throughput with a bunch of other clients. > > i noticed that earlier but rgw does not have any admin socket, i guess i'm > running defaults in this matter. Is there an option missing to have an admin > socket? 'admin socket', by default points at /var/run/ceph/$cluster-$name.asok. > > Since i was able to increase rados pool performance but not the radosgw > performance, the only thing that makes sense to me is that i forgot the > delete some configuration or something while i delete the original .rgw. > pools. All i did was 'ceph osd pool delete' is there something more to > clean? there are a bunch of pools there. 'rados lspools' will give you the list, everything that starts with .rgw is relevant. By the way, what fastcgi module are you using? Yehuda _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |