Changed the generation of hazard_curves to use the gmf_agg table #1144
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The test on Pavia cluster says that this patch works: now the post-processing phase is down to 1.5 hours (over a total runtime of 4.5 hours) in the California example provided by Damiano. Before the post-processing phase was so long to be immeasurable (the computation was stopped after 9 hours). |
|
LGTM |
micheles
added a commit
that referenced
this pull request
Apr 19, 2013
Changed the generation of hazard_curves to use the gmf_agg table
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal here is to speedup the post-processing phase, by reading the rows already aggregated in the gmf_agg table. See https://bugs.launchpad.net/oq-engine/+bug/1169703
From some experiments on my machine this change is likely to give a substantial speedup.