[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Excessive copies of set elements in GMPL
From: |
Andrew Makhorin |
Subject: |
Re: Excessive copies of set elements in GMPL |
Date: |
Thu, 16 Jul 2020 15:06:58 +0300 |
> Trying to improve GLPK/GMPL
It is a non-trivial task.
The MathProg translator included in glpk was implemented in a
non-efficient way, because there was no intention to process models
of huge size (so this allowed essentially reducing implementation
efforts).
The key idea to translate MathProg (or AMPL) models much more
efficiently is to avoid using "direct" representation of sets and
arrays and implement all operations in a way similar to one used
in relational database management systems.
> I can see that GMPL model generation is
> making an excessive number of set element copies (see bellow).
Please note that most of the copies might be temporary quantities
that exist (allocated in the memory) only during evaluation of the
(sub)expressions involving these quantities.
Best regards,
Andrew Makhorin
- Re: Excessive copies of set elements in GMPL,
Andrew Makhorin <=
- Re: Excessive copies of set elements in GMPL, Domingo Alvarez Duarte, 2020/07/16
- Re: Excessive copies of set elements in GMPL, Domingo Alvarez Duarte, 2020/07/16
- Re: Excessive copies of set elements in GMPL, Andrew Makhorin, 2020/07/16
- Re: Excessive copies of set elements in GMPL, Domingo Alvarez Duarte, 2020/07/16
- Re: Excessive copies of set elements in GMPL, Andrew Makhorin, 2020/07/16
- Re: Excessive copies of set elements in GMPL, Domingo Alvarez Duarte, 2020/07/17
- Re: Excessive copies of set elements in GMPL, Michael Hennebry, 2020/07/21
- Re: Excessive copies of set elements in GMPL, Domingo Alvarez Duarte, 2020/07/21
- Re: Excessive copies of set elements in GMPL, Michael Hennebry, 2020/07/23
- Re: Excessive copies of set elements in GMPL, Domingo Alvarez Duarte, 2020/07/24