Opened 7 years ago

Last modified 3 years ago

#4903 new defect

Memory leak?

Reported by: Andreas Nicolai <andreas.nicolai@…> Owned by: Lennart Ochel
Priority: critical Milestone:
Component: Backend Version: v1.13.0-dev-nightly
Keywords: Cc:

Description

I attached a fairly simple model that uses the AixLib for simulating a simple heat pump operation.

To run the model, within OMEdit:

  • load AixLib (either installed default lib version 0.5.2 or github version)
  • load all models in "components" subdirectory of archive
  • load HPStorage_System4.mo
  • run model (simulation time 1 year = 31536000 s, output steps 10 min = 600 s), use either colored jacobian (or numerical dense)...

When running the attached model I notice two things:

  1. performance is extremely low on Windows - model takes approx. 50 mins, OpenModelica on Linux (same machine) takes about 10 mins, whereas Dymola takes only 32 seconds... might be an indication that something is going wrong???
  1. during simulation the model continuously takes up memory starting with a few hundret Mb up to > 2 Gb of memory. That looks strange and may contribute to the performance problem.

Attachments (1)

HeatPumpTest.7z (412.3 KB ) - added by Andreas Nicolai <andreas.nicolai@…> 7 years ago.

Download all attachments as: .zip

Change History (8)

by Andreas Nicolai <andreas.nicolai@…>, 7 years ago

Attachment: HeatPumpTest.7z added

comment:1 by Martin Sjölund, 7 years ago

Try enabling the performance debugger (simulation flags -> profiler) and you see why: many non-linear torn systems taking 50~100 evaluations per step where there are calls to expensive Media functions in the algebraic loop.

comment:2 by Andreas Nicolai <andreas.nicolai@…>, 7 years ago

That would explain the poor performance. However, the continuous accumulation of memory still appears strange.

comment:3 by Francesco Casella, 6 years ago

Milestone: 1.13.01.14.0

Rescheduled to 1.14.0 after 1.13.0 releasee

comment:4 by Francesco Casella, 5 years ago

Milestone: 1.14.01.16.0

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0

comment:5 by Francesco Casella, 4 years ago

Milestone: 1.16.01.17.0

Retargeted to 1.17.0 after 1.16.0 release

comment:6 by Francesco Casella, 4 years ago

Milestone: 1.17.01.18.0

Retargeted to 1.18.0 because of 1.17.0 timed release.

comment:7 by Francesco Casella, 3 years ago

Milestone: 1.18.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.