sqlalchemy orm has an overhead associated with it
Bug #1356000 reported by
gordon chung
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ceilometer |
Fix Released
|
Wishlist
|
gordon chung | ||
Bug Description
orm has an overhead associated with it... it does a bunch of extra integrity checks and isn't designed for massive writes [1]. using sqlalchemy core provides performance closer to raw sql so we should use that for recording data.
| Changed in ceilometer: | |
| assignee: | nobody → gordon chung (chungg) |
| Changed in ceilometer: | |
| status: | Triaged → In Progress |
| Changed in ceilometer: | |
| milestone: | none → juno-rc1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to ceilometer (master) | #1 |
| Changed in ceilometer: | |
| status: | In Progress → Fix Committed |
| Changed in ceilometer: | |
| status: | Fix Committed → Fix Released |
| Changed in ceilometer: | |
| milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit b23a5476436820a
Author: gordon chung <email address hidden>
Date: Mon Aug 11 22:07:49 2014 -0400
switch to sqlalchemy core
ORM has an overhead associated with it. we need fast writes so
switch to use sqlalchemy core to improve performance.
Closes-Bug: #1356000
Change-Id: I45c76d4f294f9b