|
From: | Domingo Alvarez Duarte |
Subject: | Re: GLPSOL in webassemby faster than native ? |
Date: | Tue, 29 Sep 2020 14:13:57 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 |
Hello Andrew !I found why GLPK in wasm was faster with "--cuts" option than native, it was due wasm using qsort from muslc that is a "stable sort", I've added it to my GLPK repository and running all models in the "examples" folder only "color.mod" produces a different solution (that seems to be valid anyway).
I've update the binaries here https://github.com/mingodad/GLPK/releases/tag/qsort .
Still intriguing is that the windows 32 bits build have the performance degraded.
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 same computer program with the same data as a rule produces different results on 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] |