problem with new xcaswininst

Messages in english

Modérateur : xcasadmin

fhub
Messages : 35
Inscription : lun. juin 22, 2009 8:30 pm

problem with new xcaswininst

Message par fhub » dim. janv. 10, 2021 6:36 pm

Hi,

I'm wondering what happened to the new Xcas version (xcaswininst.exe)?
This new version is SO SLOW that it's in fact unusable!

It happens with lots of files loaded via 'Help > Examples' - e.g. demo\calcform.xws:
After loading this file in the previous versions (installed with xcasinst.exe or xcas64inst.exe), the calcsheet is calculated and loaded immediately (around 1 sec) - with the new version from xcaswininst.exe it needs 3:35 min until it appears!

And that's not the only file which takes incredibly long ...

Franz

parisse
Messages : 5336
Inscription : mar. déc. 20, 2005 4:02 pm
Contact :

Re: problem with new xcaswininst

Message par parisse » lun. janv. 11, 2021 7:45 pm

Perhaps something related to Unix vs Windows newlines when loading files, I will investigate.

parisse
Messages : 5336
Inscription : mar. déc. 20, 2005 4:02 pm
Contact :

Re: problem with new xcaswininst

Message par parisse » mer. janv. 13, 2021 5:13 pm

The parser is way slower than with cygwin, I have no idea why : it's exactly the same bison/flex output than on Unix or with cygwin.

fhub
Messages : 35
Inscription : lun. juin 22, 2009 8:30 pm

Re: problem with new xcaswininst

Message par fhub » mer. janv. 13, 2021 7:11 pm

parisse a écrit :
mer. janv. 13, 2021 5:13 pm
The parser is way slower than with cygwin, I have no idea why : it's exactly the same bison/flex output than on Unix or with cygwin.
Ive already seen such compiler differences in some other programs:
e.g. the program DosBox-X contains several different versions, and the VS build is about 2.5 tmes slower than the MinGW version.

I don't understand why you've changed your compiler (as I can see on all these new DLLs), when the previous version worked much better!?
But ok, no problem for me - I'll just stay with your old versions xcasinst and xcas64inst, and not update Xcas anymore ...

Franz

parisse
Messages : 5336
Inscription : mar. déc. 20, 2005 4:02 pm
Contact :

Re: problem with new xcaswininst

Message par parisse » mer. janv. 13, 2021 7:30 pm

Actually the cygwin compiler has it's own problems. For example, many users report that the 64 bits version does not work with their version of windows and must use the 32 bits version. There are also problems with 3d.
The mingw version is an attempt to fix these problems. It is still in tests, and the slowness problem is a serious problem. I will keep compiling the cygwin version. Unless I or someone else find a workaround.

parisse
Messages : 5336
Inscription : mar. déc. 20, 2005 4:02 pm
Contact :

Re: problem with new xcaswininst

Message par parisse » jeu. janv. 14, 2021 8:23 am

Good news! I found why the parser was slow: it's inside the chartab2gen function in gen.cc, parsing floats was done with a mutex protection, and the mutex check is very slow. But it can be disabled in mingw. I will update xcaswininst.exe soon.

fhub
Messages : 35
Inscription : lun. juin 22, 2009 8:30 pm

Re: problem with new xcaswininst

Message par fhub » jeu. janv. 14, 2021 3:11 pm

Good news? Not really ...
I've now tested the new version of today, and it's only a bit faster -
it still needs ~2 min compared to 1 sec in the 64bit version (or the old 32bit version).

IMO there must be any other serious problem, because parsing a file can't take more than 100-times longer.

Edit: I've now made a few tests (changing the commands in calcform.xws), and the problem seems to be the
commands 'plot(...)' and 'plotfield(...)' with their huge datasets.
If I remove those commands, then the file loads quickly as usual.

parisse
Messages : 5336
Inscription : mar. déc. 20, 2005 4:02 pm
Contact :

Re: problem with new xcaswininst

Message par parisse » jeu. janv. 14, 2021 5:40 pm

Indeed, giacxcas.dll was not updated. Should be fixed now.

fhub
Messages : 35
Inscription : lun. juin 22, 2009 8:30 pm

Re: problem with new xcaswininst

Message par fhub » jeu. janv. 14, 2021 6:04 pm

Yep, now it's working again - many thanks! :-)

Regards,
Franz

Répondre