Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -17,7 +17,7 @@
17	17	Model
18	18	)))|=(((
19	19	Sim length (s)
20		-)))|=Regions|=Nr simulations|=Nr workers|=Execution time (hh:mm)
	20	+)))|=Nodes|=Nr simulations|=Nr workers|=Execution time (hh:mm)
21	21	|=MontbrioPazoRoxin|30|100|(((
22	22	30
23	23	)))|30|00:17
...	...	@@ -28,10 +28,9 @@
28	28	|=MontbrioPazoRoxin|30|100|500|55|01:30
29	29	|=MontbrioPazoRoxin|30|100|600|55|01:45
30	30	|=MontbrioPazoRoxin|30|100|600|60|OOM
31		-|=MontbrioPazoRoxin|60|100|500|40|(((
32		-03:07
	31	+|=MontbrioPazoRoxin|60|100|500|55|(((
	32	+OOM
33	33	)))
34		-|MontbrioPazoRoxin|60|100|500|55|OOM
35	35	| | | | | |
36	36	| | | | | |
37	37	| | | | | |
...	...	@@ -46,14 +46,14 @@
46	46	| | | | | |
47	47	| | | | | |
48	48	| | | | | |
	48	+| | | | | |
49	49
50		-==== ====
51	51
52	52	==== 2. Limitations ====
53	53
54	54	* Reaching he memory limit on the CSCS node.
55		-** For a simulation of 30 seconds, we can fit 55 parallel workers in the available memory
56		-** For a simulation of 60 seconds, we can fit 40 parallel workers in the available memory
	54	+** For a simulation of 30 seconds, we can fit 55 parallel workers in the available memory.
	55	+** For a simulation of 60 seconds, we can fit 40 parallel workers in the available memory.
57	57	* Reaching the maximum connections on CSCS could happen during a run
58	58	** connect once to launch the job
59	59	** connect multiple times during the monitoring step to check the status of the job