Opened 9 years ago
Last modified 8 years ago
#4076 new defect
Really bad performance with big tables
| Reported by: | Adrian Pop | Owned by: | somebody |
|---|---|---|---|
| Priority: | high | Milestone: | Future |
| Component: | *unknown* | Version: | |
| Keywords: | Cc: |
Description
Flattening and compilation of models including big tables takes a lot of time and a lot of memory. The attached model takes ~4h to compile.
Most of the time is spent in functions that test if an expression is constant or in simplifications.
Attachments (1)
Change History (4)
by , 9 years ago
| Attachment: | SensorBlockIncludeMap1.mo added |
|---|
comment:1 by , 9 years ago
comment:2 by , 8 years ago
See also the recently added TimeTable_N_XXX and CombiTimeTable_N_XXX models in the ScalableTestSuite. They seem to have a real problem with front-end scaling time.
Note:
See TracTickets
for help on using tickets.
The only solution I'm seeing for this is to extend the DAE array and matrix type to include a constantness flag so we don't do the same thing over and over.