d4d9457aa1
This was explored as part of discussion with zzzeek on various ways to make a statement with a large in_ be more performant. Batching the queries by chunking rp_ids did not help, but an expanding bindparam did: it makes the surrounding method about 50% faster [1]. bindparam expanding was added in sqlalchemy 1.2.0 so we bump the requirements here to the latest 1.2.x bugfix release, 1.2.19. [1] With the caveat that profiling and benchmarking are very different things, and in this case it is profiling results which are being analysed. Change-Id: Ic4e0cdd87f8f2d76b921059ac4bf16a838913abf
28 lines
1.1 KiB
Plaintext
28 lines
1.1 KiB
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
SQLAlchemy>=1.2.19 # MIT
|
|
keystonemiddleware>=4.18.0 # Apache-2.0
|
|
Routes>=2.3.1 # MIT
|
|
WebOb>=1.8.2 # MIT
|
|
jsonschema<3.0.0,>=2.6.0 # MIT
|
|
requests>=2.14.2 # Apache-2.0
|
|
six>=1.10.0 # MIT
|
|
setuptools!=24.0.0,!=34.0.0,!=34.0.1,!=34.0.2,!=34.0.3,!=34.1.0,!=34.1.1,!=34.2.0,!=34.3.0,!=34.3.1,!=34.3.2,!=36.2.0,>=21.0.0 # PSF/ZPL
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.config>=6.7.0 # Apache-2.0
|
|
oslo.context>=2.19.2 # Apache-2.0
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|
|
oslo.utils>=3.37.0 # Apache-2.0
|
|
oslo.db>=4.40.0 # Apache-2.0
|
|
oslo.policy>=1.35.0 # Apache-2.0
|
|
oslo.middleware>=3.31.0 # Apache-2.0
|
|
oslo.upgradecheck>=0.2.0 # Apache-2.0
|
|
# NOTE(efried): Sync lower-constraints.txt for os-traits & os-resource-classes.
|
|
os-resource-classes>=0.5.0 # Apache-2.0
|
|
os-traits>=0.16.0 # Apache-2.0
|
|
microversion-parse>=0.2.1 # Apache-2.0
|