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
..
account	Replace xrange() with six.moves.range()	2015-06-23 07:29:15 +00:00
cli	Add ring-builder analyzer.	2015-07-02 08:16:03 -07:00
common	Merge "Make logic of unit tests responsive to the method names"	2015-07-15 07:39:24 +00:00
container	Merge "Replace dict.iteritems() with dict.items()"	2015-07-09 18:36:05 +00:00
obj	do container listing updates in another (green)thread	2015-07-22 01:19:58 -07:00
proxy	Merge "Replace dict.iteritems() with dict.items()"	2015-07-09 18:36:05 +00:00
test_locale	Replace dict.iteritems() with dict.items()	2015-06-24 09:39:55 +02:00
__init__.py	Replace xrange() with six.moves.range()	2015-06-23 07:29:15 +00:00