Thanks Andrew, Got it, your answer explained the reason why multilple executor from clients improve overall performance in my environment. So incrementing PROPERTY_IO_WORKER_THREADS and others similiar properties have no meaning in 1.7.0 and further ?
-sumit On Fri, Jan 10, 2014 at 10:46 AM, Andrew Phillips <[email protected]>wrote: > Hi Sumit > > As part of jclouds 1.7 and 1.8, quite a few things are changing on the > thread management front in jclouds. Where previously there were both > synchronous and asynchronous versions of APIs (such as the Swift API) > running via executors managed by jclouds, we're now moving more towards an > approach where thread and executor management will be handled by the caller. > > Blobstore will continue to support some asynchronous calls, but in terms > of improving performance, my suggestion would be to stick to the > synchronous calls and use your own executors. An example that could be > relevant is here [1]. > > I'm not the blobstore performance expert, though - hopefully, one of those > will be able to contribute to this thread. > > Regards > > ap > > [1] https://github.com/jclouds/jclouds-cloud-storage-workshop/blob/master/ > exercise2/src/main/java/org/jclouds/labs/blobstore/ > exercise2/MultiFileUploaderC.java >
