being actively maintained is one of the review criteria; I've raised aodh and ceilometer tasks as it would appear that this might not be the case today (things where being actively maintained 2 years ago when ujson was added to global requirements).
Any opinion from the OpenStack telemetry devs? are the performance gains from ujson sufficient to justify using something other than the standard json module?
Reading the original inclusion commit:
https:/ /github. com/openstack/ requirements/ commit/ f610e12d67fc093 b713c442da2d973 da6d71e0ab
being actively maintained is one of the review criteria; I've raised aodh and ceilometer tasks as it would appear that this might not be the case today (things where being actively maintained 2 years ago when ujson was added to global requirements).
Any opinion from the OpenStack telemetry devs? are the performance gains from ujson sufficient to justify using something other than the standard json module?