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
The FAIMMS harvester is running database queries which generate an unreasonable amount of load on the database server.
aodn/data-services#742 will mitigate the impact somewhat, however the harvester must be updated in order to perform more optimally.
The queries seem to run relatively quickly, but while running, the DELETE query very quickly consumes nearly all of the available Postgres buffer pool memory, causing every other connection to slow to a crawl.
The problematic queries are the ones that look like:
harvest=# select query from database_activity();
query
-------------------------------------------------------------------------------------------------------------DELETEFROM measurements_qaqc where measurement IN (with duplicates as (select channel_id, "TIME", count(*)+from measurements_qaqc +group by channel_id, "TIME"+HAVINGcount(*) >1) +selectmin(measurements_qaqc.measurement) +from duplicates,measurements_qaqc +where measurements_qaqc."TIME"= duplicates."TIME"ANDmeasurements_qaqc.channel_id=duplicates.channel_id+GROUP BYduplicates.channel_id, duplicates."TIME")
I'd suggest we need to rework this query on a copy of the whole schema such that it consumes substantially less memory!
The text was updated successfully, but these errors were encountered:
The FAIMMS harvester is running database queries which generate an unreasonable amount of load on the database server.
aodn/data-services#742 will mitigate the impact somewhat, however the harvester must be updated in order to perform more optimally.
The queries seem to run relatively quickly, but while running, the DELETE query very quickly consumes nearly all of the available Postgres buffer pool memory, causing every other connection to slow to a crawl.
The problematic queries are the ones that look like:
I'd suggest we need to rework this query on a copy of the whole schema such that it consumes substantially less memory!
The text was updated successfully, but these errors were encountered: