Risk calculators may be dominated by the asset<->site association queries

[Michele Simionato]

This is a big issue in at least three scenario damage calculations:

   oq_job_id | description | tot_duration
  -----------+--------------------------------+------------------
         309 | Scenario Risk Portugal onshore | 154171.976270907
         310 | Scenario Risk Portugal onshore | 6545137.67178791
         327 | Scenario Risk Portugal onshore | 2483490.77708211

In such computation the 99% of the time is spent there.

[Michele Simionato (michele-simionato)]

Actually the computations where the associating time is bigger than the GMF-retrieving time are many; and in particular the computation of our sponsor Hannover RE is in this category:

   oq_job_id | description | associating | getting_gmvs
  -----------+----------------------------------------------------------------------------------------+------------------+-------------------
         269 | Malaysia all Zones and country, Vuln=my1 final, resolution=sites (population weighted) | 19191.6752510078 | 3735.10616826949

Idem for the event based risk computation by Shriram.

[Michele Simionato (michele-simionato)]

First of all the monitoring was fixed here: https://github.com/gem/oq-engine/pull/1404

[Michele Simionato (michele-simionato)]

The asset<->site association queries have been optimized a lot by running them once per taxonomy, not once per block of assets. See https://github.com/gem/oq-engine/pull/1415