[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Fwd: Re: Solver performance solving examples/life_goe.mod]
From: |
Andrew Makhorin |
Subject: |
[Fwd: Re: Solver performance solving examples/life_goe.mod] |
Date: |
Sat, 26 Sep 2020 18:26:42 +0300 |
-------- Forwarded Message --------
From: Jeffrey Kantor <jeff.kantor@gmail.com>
To: Chris Matrakidis <cmatraki@gmail.com>
Cc: Domingo Alvarez Duarte <mingodad@gmail.com>, help-glpk@gnu.org <help
-glpk@gnu.org>
Subject: Re: Solver performance solving examples/life_goe.mod
Date: Sat, 26 Sep 2020 10:23:18 -0400
> Will there be a point where the GLPK package will be opened for
> collaborative development using, say, GitHub?
>
> > On Sep 26, 2020, at 10:20 AM, Chris Matrakidis <cmatraki@gmail.com>
> > wrote:
> >
> > I made some performance improving patches a few years ago. You can
> > find them in: https://github.com/cmatraki/GLPK
> >
> > Best Regards,
> >
> > Chris Matrakidis
> >
> > On Sat, 26 Sep 2020 at 14:54, Domingo Alvarez Duarte <mingodad@gmail
> > .com> wrote:
> > > Hello !
> > >
> > > Testing GLPK I left it solving examples/lie_goe.mod for more than
> > > 2
> > > hours and it didn't found a solution (wasm and native) then I
> > > stopped
> > > then and tried with cplex/gurobi/xpress/scip all of then gives a
> > > solution instantly (except scip that takes 3s).
> > >
> > > The difference is so big, have someone managed through command
> > > line
> > > options or other means managed to get a solution quickly with
> > > glpsol ?
> > >
> > > Any idea of how to improve GLPK to not be so behind ?
> > >
> > > Cheers !
> > >
> > >
> > >
>
>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Fwd: Re: Solver performance solving examples/life_goe.mod],
Andrew Makhorin <=