Opened 10 years ago
Closed 5 years ago
#2773 closed defect (fixed)
Linear tearing slower than not using it
| Reported by: | Martin Sjölund | Owned by: | Willi Braun |
|---|---|---|---|
| Priority: | high | Milestone: | Future |
| Component: | Backend | Version: | trunk |
| Keywords: | Cc: | Lennart Ochel |
Description
In r21558, linear tearing was enabled. This increased the time that Modelica.Electrical.Spice3.Examples.Spice3BenchmarkFourBitBinaryAdder.mos takes to run (from being the slowest test at 4m52s, up to 6m10s).
Change History (11)
comment:1 by , 10 years ago
| Milestone: | 1.9.1 → 1.9.2 |
|---|
comment:2 by , 10 years ago
| Milestone: | 1.9.2 → 1.9.3 |
|---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:7 by , 8 years ago
| Milestone: | 1.11.0 → 1.12.0 |
|---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:8 by , 7 years ago
| Milestone: | 1.12.0 → Future |
|---|
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
comment:9 by , 5 years ago
I think tearing for linear componets is not in the master any more.
I added linear tearing as an optional feature, controlled by flag LSanalyticJacobian which defaults to off in this PR https://github.com/OpenModelica/OpenModelica/pull/271/commits/c2ed046bb04bbf24558c56d9ba7f08d57a6361b6.
I'm trying to check if tearing and using sparsity pattern for linear loops affects the performance for parallel jacobian evaluation.
comment:10 by , 5 years ago
Added Commit 6604e0d34 to master.
I think we can close this ticket now.
comment:11 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).