You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For large CKAN installations that use the Datastore and use postgresql replication, performance/concurrency has been vastly improved with the introduction of datastore.write_url and datastore.read_url set to the master and replica respectively.
Performance/concurrency can be further improved by allowing "dirty reads" of the datastore. This can be done by setting the SQLAlchemy engine isolation level to "READ_UNCOMMMITTED" for the read_url connection.
Installations that don't employ Postgres replication for the Datastore should also benefit from this change.
The text was updated successfully, but these errors were encountered:
For large CKAN installations that use the Datastore and use postgresql replication, performance/concurrency has been vastly improved with the introduction of
datastore.write_url
anddatastore.read_url
set to the master and replica respectively.Performance/concurrency can be further improved by allowing "dirty reads" of the datastore. This can be done by setting the SQLAlchemy engine isolation level to "READ_UNCOMMMITTED" for the read_url connection.
Installations that don't employ Postgres replication for the Datastore should also benefit from this change.
The text was updated successfully, but these errors were encountered: