Measure the performance drop of using python logic tree processor with java source model parser
Bug #856345 reported by
Anton Gritsay
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenQuake (deprecated) |
Fix Released
|
Medium
|
Anton Gritsay |
Bug Description
-
Changed in openquake: | |
milestone: | none → 0.5.0 |
Changed in openquake: | |
importance: | Undecided → Medium |
Changed in openquake: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We can avoid instantiating a lot of java objects through jpype if we just reparse source model files every time we need to modify their values. The overhead is still manageable: parsing california_ fault_model. xml (1478 sources, 1662739 bytes) takes 280 ms, parsing SEAsiaGSHAP.xml (398 sources, 571688 bytes) takes 185 ms and Myanmar.trial1.xml (44549 sources, 96477898 bytes) takes 8837 msec. Heavy files with many point sources are slow to parse, however, they are not likely to be used with complex logic trees.