Efficient limiting using SQL

Registered by Brian Lamar on 2011-06-17

Currently API limits are done after all results are returned from SQL. For example if the request was http://localhost:8774/v1.0/servers/detail?limit=50 and there were 10,000 servers to be returned, the API would request all 10,000 servers from the database, buffer them all in memory, and return only the first 50.

This can be better handled by passing the limits down to the SQL layer and doing more efficient queries.

Blueprint information

Status:
Complete
Approver:
Vish Ishaya
Priority:
Low
Drafter:
None
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
Accepted for folsom
Implementation:
Implemented
Milestone target:
None
Started by
Yaguang Tang on 2012-06-06
Completed by
Russell Bryant on 2012-11-02

Related branches

Sprints

Whiteboard

Seems totally reasonable, we just need someone to take it on.

Gerrit topic: https://review.openstack.org/#q,topic:bp/efficient-limiting,n,z

Addressed by: https://review.openstack.org/10523
    Implement bp:efficient-limiting.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.