swift/test
John Dickinson 2289137164 do container listing updates in another (green)thread
The actual server-side changes are simple. The tests are a different
matter. Many changes were needed to the object server tests to
handle the now-async calls to the container server. In an effort to
test this properly, some drive-by changes were made to improve tests.

I tested this patch by doing zero-byte object writes to one container
as fast as possible. Then I did it again while also saturating 2 of the
container replica's disks. The results are linked below.

https://gist.github.com/notmyname/2bb85acfd8fbc7fc312a

DocImpact

Change-Id: I737bd0af3f124a4ce3e0862a155e97c1f0ac3e52
2015-07-22 01:19:58 -07:00
..
functional Merge "Select policy when running functional test" 2015-07-17 00:26:44 +00:00
probe Merge "Replace dict.iteritems() with dict.items()" 2015-07-09 18:36:05 +00:00
unit do container listing updates in another (green)thread 2015-07-22 01:19:58 -07:00
__init__.py In-process swift server for functional tests 2014-04-29 08:45:11 -04:00
sample.conf Minor change to the service token sample test config 2015-02-27 11:54:50 +00:00