efficient measures post api

Bug #1641169 reported by gordon chung
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gnocchi
Triaged
Wishlist
Unassigned

Bug Description

just to put to paper, we discussed a new endpoint for highly 'efficient' posting of measures. currently we post json in rather verbose way {timestamp: <time>, value: <value>},.... this works fine but if we didn't have to do so much parsing it could be even better.

possibly something like some binary serialized epochtime:value pair.

gordon chung (chungg)
Changed in gnocchi:
status: New → Triaged
importance: Undecided → Wishlist
Changed in gnocchi:
assignee: nobody → fengchaoyang (fengchaoyang)
assignee: fengchaoyang (fengchaoyang) → nobody
Revision history for this message
yxu (xuyao18) wrote :

When we are using ceilometer and gnocchi to store measure, I found querying metric and storing data will cost a lot time ,especially when a batch data is coming , which will cost a lot time to query metric and update metric.

e.g. when batch size is 50, the worst situation is querying metric costs about 15 seconds , it is not efficient.

I assume that could we use something like message queue to buffer measure, or some other way to reduce time cost by storing measures .

Revision history for this message
Julien Danjou (jdanjou) wrote :

Querying has no relationship whatsoever with the size of incoming batch.
Can you be more precise about what you do exactly yxu?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.