Sumit, I realize that you had sent out a similar email sometime ago about performance degradation. I'm not sure if anyone has run these types of long running experiments with jclouds. So this may be a first.
The 409 status is returned because of a conflict [1]. Are you sure you didn't have two or more threads trying to delete the same object? Also, I see that that 409 is returned by Swift if you try to delete a container that isn't empty[2]. Is that something your test code could've tried? When you say there was a similar test you're trying with curl, are you using the curl command-line utility or the libcurl library? How are you specifying the number of threads to use and what object each thread should get/put/delete? Thanks. -Shri [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html [2] https://bugs.launchpad.net/horizon/+bug/1096084 On Sun, Apr 20, 2014 at 5:55 PM, Sumit Gaur <[email protected]> wrote: > Hi > I using jclouds lib integrated with Openstack Swift+ keystone combinaiton. > Things are working fine except stability test. After 20-30 hours of test > jclouds/SWIFT start degrading in TPS and keep going down over the time. > > 1) I am running the (PUT-GET-DEL) cycle in 10 parallel threads. > 2) I am getting a lot of 409 and DEL failure for the as response too from > SWIFT. > 3) Direct similiar test from curl does not show much impact and TPS remain > constant. > > Can sombody help me wht is going wrong here ? > > Thanks > sumit
