Currently the SQL backend lists revoked tokens by selecting all of the
columns, including the massive "extra" column. This places a significant
burden on the client library and wastes resources. We only need the
id/expired columns to satisfy the API call.
In tests this query was several orders of magnitude faster with just two
thousand un-expired revoked tokens.
Reviewed: https:/ /review. openstack. org/57976 github. com/openstack/ keystone/ commit/ ab7221246af394f 24e47484e822b8d cda37411aa
Committed: http://
Submitter: Jenkins
Branch: master
commit ab7221246af394f 24e47484e822b8d cda37411aa
Author: Clint Byrum <email address hidden>
Date: Fri Nov 22 08:50:39 2013 -0800
Narrow columns used in list_revoked_tokens sql
Currently the SQL backend lists revoked tokens by selecting all of the
columns, including the massive "extra" column. This places a significant
burden on the client library and wastes resources. We only need the
id/expired columns to satisfy the API call.
In tests this query was several orders of magnitude faster with just two
thousand un-expired revoked tokens.
Change-Id: I04d62b98d5d760 a3fbc3c8db61530 f7ebccb0a48
Closes-Bug: #1253755