|
From: | Domingo Alvarez Duarte |
Subject: | Re: GLPSOL in webassemby faster than native ? |
Date: | Tue, 22 Sep 2020 15:03:47 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 |
Hello Tor ! Thanks for reply ! Do you know why that happen ? Which criteria is used to select one ? Can we somehow force/direct the solver to adopt a different one ? Cheers ! On 22/9/20 14:03, Tor Myklebust wrote:
Note that the two solvers made different branching decisions once it came time to solve the MIP.On Tue, 22 Sep 2020, Domingo Alvarez Duarte wrote:Hello Andrew !Due to the big difference in solver time how could we figure out what's is it in order to use this knowledge to improve the native solver time ?I mean what debug/verbose options could help us have a clue ? Cheers ! On 21/9/20 17:11, Andrew Makhorin wrote:On Mon, 2020-09-21 at 16:09 +0200, Domingo Alvarez Duarte wrote:Hello Andrew ! Are you saying that floating point calculations are more efficient/precise in webassembly ?No. I meant that due to floating-point computations running the samecomputer program with the same data as a rule produces different resultson different platforms.Cheers ! On 21/9/20 15:08, Andrew Makhorin wrote:Does someone can give a possible explanation ?floating-point computations
[Prev in Thread] | Current Thread | [Next in Thread] |