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
Upon investigating image-service tiling speed which was around 1 image per ~23 seconds, realised that there are 1.3m images without tiles that can be extracted by the following query:
SELECTCOUNT(*) AS cnt,
i.data_resource_uidFROM
image i
LEFT JOIN
audit_message am
ONi.image_identifier=am.image_identifierANDam.messagelike'TMS%'WHEREi.zoom_levels=0ANDam.image_identifier IS NULLGROUP BYi.data_resource_uidORDER BY
cnt DESCLIMIT100
and the result includes 55 data resources. Here is the snapshot from the top records:
As per @sbearcsiro 's great work, the tiling queue which was running super slow last week is all tiled and the queue is back to 0 now. But seems that restarting image service will lose the items in the queue and this could have happened many times in the pas due to restarts.
The issue here is the address the tiling task which needs to be resilient against restarts and also its performance should be much higher that the speed of ingesting images into the system.
The text was updated successfully, but these errors were encountered:
Upon investigating image-service tiling speed which was around 1 image per ~23 seconds, realised that there are 1.3m images without tiles that can be extracted by the following query:
and the result includes 55 data resources. Here is the snapshot from the top records:
As per @sbearcsiro 's great work, the tiling queue which was running super slow last week is all tiled and the queue is back to
0
now. But seems that restarting image service will lose the items in the queue and this could have happened many times in the pas due to restarts.The issue here is the address the tiling task which needs to be resilient against restarts and also its performance should be much higher that the speed of ingesting images into the system.
The text was updated successfully, but these errors were encountered: