Opened 8 years ago
Closed 8 years ago
#4225 closed defect (invalid)
Scalable Testsuite decrease
Reported by: | vwaurich | Owned by: | lochel |
---|---|---|---|
Priority: | high | Milestone: | Future |
Component: | Backend | Version: | |
Keywords: | Cc: | lochel, ptaeuber, wbraun, sjoelund.se |
Description
Hi,
https://test.openmodelica.org/libraries/ScalableTestSuite_Experimental/BuildModelRecursive.html
The coverage dcreased since 17/01. It doesnt seem to be due to resolveLoops. I optimized it a bit and it seems fairly ok.
remoSimpleEquations is memory intense and tearing takes very long.
Check out ScalableTestSuite.Electrical.DistributionSystemDC.ScaledExperiments.DistributionSystemModelica_N_40_M_40:
Notification: Performance of preOpt removeSimpleEquations (simulation): time 3.776/28.61, allocations: 11.08 GB / 14.93 GB, free: 95.48 MB / 0.8809 GB Notification: Performance of preOpt resolveLoops (simulation): time 3.361/34.42, allocations: 17.78 MB / 15.4 GB, free: 2.438 MB / 0.9122 GB Notification: Performance of postOpt tearingSystem (initialization): time 80.75/117.4, allocations: 2.767 GB / 18.6 GB, free: 122.6 MB / 0.9122 GB
Change History (6)
comment:1 Changed 8 years ago by wbraun
comment:2 Changed 8 years ago by vwaurich
The number of compiling and simulating models reduced from 16/01 to 18/01. Results are not verified for the scalable testsuite. Which configuration changed? Maybe the timeout?
comment:3 Changed 8 years ago by wbraun
In this case the parameter maxSizeLinearTearing has changed. Also note that the ScalableTestSuite is always started manually.
comment:4 Changed 8 years ago by vwaurich
- Resolution set to fixed
- Status changed from new to closed
I see. Then there is nothing to do. Thanks for information. I will close the ticket.
comment:5 Changed 8 years ago by lochel
- Resolution fixed deleted
- Status changed from closed to reopened
comment:6 Changed 8 years ago by lochel
- Resolution set to invalid
- Status changed from reopened to closed
Which results are you comparing? Since the last 10 times this test runs with different configuration.