oq run stuck on classical 44% but not resource is being used

52 views
Skip to first unread message

Nima Dolatabadi

unread,
Jun 1, 2024, 3:01:30 PMJun 1
to OpenQuake Users
i am runing a hazard calculation and the log is: 

[2024-06-01 00:31:48 #7 INFO] classical  11% [9 submitted, 0 queued]
[2024-06-01 00:35:49 #7 INFO] classical  22% [9 submitted, 0 queued]
[2024-06-01 00:40:33 #7 INFO] classical  33% [9 submitted, 0 queued]
[2024-06-01 00:44:48 #7 INFO] classical  44% [9 submitted, 0 queued]

but no cpu or ram usage is being shown. using top command on linux
what is the problem here?

i have attached the image of both issus.
Regards
NimaScreenshot from 2024-06-01 22-21-52.pngScreenshot from 2024-06-01 22-21-57.png

Peter Pažák

unread,
Jun 1, 2024, 6:25:17 PMJun 1
to openqua...@googlegroups.com
Hi,

for us this quite often happens - but on Windows. Most of the time it means some of the subjobs run out of memory
but the main process did not get information about it - still waiting to get result from those subjobs which died.
You should see how many concurrent tasks the engine used in the listing above and if you did not set it, try to increase (maybe double?)
the number of concurrent tasks in the ini file for example:
concurrent_tasks = 500
That may help avoid this hanging behaviour.
Please also always note the OQ version you are using in your post
so that it is clear you are not using a version that had some bugs which were eventually later corrected.

Peter



so 1. 6. 2024 o 21:01 Nima Dolatabadi <610590...@gmail.com> napísal(a):
--
You received this message because you are subscribed to the Google Groups "OpenQuake Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openquake-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openquake-users/d4a7c8c2-9eaf-4db8-90c1-f629491f3c92n%40googlegroups.com.

Nima Dolatabadi

unread,
Jun 2, 2024, 5:35:01 AMJun 2
to OpenQuake Users
i am using openquake.engine==3.19
is there any possibilty to break down the proccess or using gpu? I have defined a very dense grid and i need it for the analysis. I cannot lower the resoloution.
regards
Nima

Peter Pažák

unread,
Jun 5, 2024, 3:52:56 PMJun 5
to OpenQuake Users
Exactly this parameter concurrent_tasks breaks the task into smaller pieces...

Peter

Dátum: nedeľa 2. júna 2024, čas: 11:35:01 UTC+2, odosielateľ: Nima Dolatabadi
Reply all
Reply to author
Forward
0 new messages