gord chung 3332206969 ceph: store measures in omap values ... ceph sucks for small objects; POSTs to ceph incoming are always small objects. this changes logic to store new measures as omap values instead of objects. this allows us to write to 'memory' aka leveldb/rocksdb instead of disk. this does not change the durability agreement since we are already storing object keys in omap so if omap fails, we will lose link to objects regardless if on disk or not. using local 20OSD ceph cluster, with 18 metricd. this is: - ~2x faster than aio_write patch to POST - ~2x faster than aio_write patch to process - ~3x faster than no aio_write patch to POST - ~3x faster than no aio_write patch to process - ~3.5x faster than 3.1 to POST - something a lot faster than 3.1 to process (no idea why) Change-Id: I4bae365955fdbafe4ad837596490774c42bc5251		2017-05-16 15:39:09 +00:00
..
__init__.py	push incoming into different sacks	2017-05-10 20:06:40 +00:00
_carbonara.py	drop metric lock	2017-05-15 16:00:51 +00:00
ceph.py	ceph: store measures in omap values	2017-05-16 15:39:09 +00:00
file.py	drop metric lock	2017-05-15 16:00:51 +00:00
redis.py	drop metric lock	2017-05-15 16:00:51 +00:00
s3.py	drop metric lock	2017-05-15 16:00:51 +00:00
swift.py	drop metric lock	2017-05-15 16:00:51 +00:00