Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
huge performance penalty in windows XP - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Tue Aug 8th, 2017 03:04 pm
PM Private Upload Quote Reply
drwho
Member
 

Joined: Fri Feb 8th, 2008
Location:  
Posts: 101
Status: 
Offline
hi,
i'm migrating a D7 application using sisulizer 3 to
D10 (tokyo) using sisulizer 4 (build 386)

now both builds are sisulized with embedded translated resource dll's which i extract at program start

now the D7 translated version runs as expected, almost identical in speed as the native non translated exe

the D10 version runs about 20 times slower when opening certain forms, when using embedded resource dll's on windows XP (we still have to support that platform)
if i run this on W10 all goes well...
if i build a D10 translated exe this runs also well on windows XP
so there must be a difference in how windows XP handles these new embedded resource dll's

any idea on how to fix this?

tia,
marc

Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 8th, 2017 03:35 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Since the loading of the embedded DLLs is part of Delphi's logic is not much we can do here except that some other customer has some work around. I guess is, that if you ask the makers of the VCL the will tell you, that XP is no longer supported.

You might want to try the build variation with external resource DLLs that are not embedded into the EXE. If this is faster than you at least know, that the extraction takes the extra time. My guess then is, that VCL tries to extract to some folder, doesn't have enought rights on XP, then tries in the next folder... But this is just guessing.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 9th, 2017 06:00 am
PM Private Upload Quote Reply
drwho
Member
 

Joined: Fri Feb 8th, 2008
Location:  
Posts: 101
Status: 
Offline
imho it has nothing to do with the vcl wanting to extract to some folder
i'm doing the extraction in code before any form is created
if not they would not be translated at all, wouldn't they?

the fact that xp is no longer supported is a bit silly, XP is still alive and kicking and some of us do not have the luxury to ban all clients still using XP

if i have to randomly pick a reason i would look at the fact that D10 is unicode and i see that the sisu project forces the use of unicode for D10
so potentially there is a flaw in the sisu code with respect to that...

is this forum officially monitored by sisulizer?

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 9th, 2017 08:43 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Sisulizer does not change the logic of your code or adds code. The whole localization logic at runtime is in the VCL. Sisulizer just replaces the ressources in your binaries which are always in UNICODE. Sisulizer prepares the ressources the way VCL needs them. To my knowledge it can't force VCL or your app in any way, but I ask our R&D to make sure.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 9th, 2017 08:43 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Sisulizer does not change the logic of your code or adds code. The whole localization logic at runtime is in the VCL. Sisulizer just replaces the ressources in your binaries which are always in UNICODE. Sisulizer prepares the ressources the way VCL needs them. To my knowledge it can't force VCL or your app in any way, but I ask our R&D to make sure.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 9th, 2017 08:47 am
PM Private Upload Quote Reply
drwho
Member
 

Joined: Fri Feb 8th, 2008
Location:  
Posts: 101
Status: 
Offline
i dig that but the fact is that there must be some change in either D7 vs D10
or
sisu 3 vs sisu 4
that makes the use of resource dll's a lot slower
i'm talking 3 to 5 times slower on windows XP
and not in all forms, i really can't pinpoint it to one component or 1 form ...

on windows 10 there is no difference at all... (tested on W7 also)
so it must be windows XP that is the trigger somehow...

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 9th, 2017 09:31 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Regarding dropped XP support. I meant that the support for XP was droppe by Microsoft and the makers of Delphi.

http://docwiki.embarcadero.com/PlatformStatus/en/Main_Page

There might be changes in the VCL. Everything is going to internal UNICODE support and XP did not fully supported it. There had been many improvements in the OSs regarding localization support and from a localization view it is good to see XP fade.

Sisulizer itself is build using a not to new Delphi version. We simply don`t have Windows 2000 and XP in the officially supported list since we don`t test it with these oldies anymore.

You can do a quick test. Start Sisulizer 4 on XP. It is localized with Sisulizer 4, uses embedded ressources and is build with a pre-Delphi 10 version.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 9th, 2017 09:36 am
PM Private Upload Quote Reply
drwho
Member
 

Joined: Fri Feb 8th, 2008
Location:  
Posts: 101
Status: 
Offline
i would love to have not to support XP any longer
but the fact is that for a closed system there is no need to move to other windows version

it is easy to say that support is dropped, but the fact is that for certain big instances MS is still supporting XP up to date...

anyway if D10 is the culprit than there's not much sisu can do about it...

testing Sisu4 on D7: can do that but this will only rule out the sisu fact - which is maybe a good thing to do, i'll see if i find some time to do this and when so i'll report back

thx for the feedback..

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 9th, 2017 09:44 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
I meant simply starting the Sisulizer 4 eval on XP. If it starts fast your issue is an issue of the newer VCL you use. Using an older Delphi with XP support will then help.
Right now we do not have complains about Sisulizer 4 starting slow on XP or 2000.

As you see we try to help with older OSs. But in contrast to Microsoft or the makers of Delphi we are tiny and our influence (and other localization tools) on them is near zero. So we are in the same boat.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 9th, 2017 10:16 am
PM Private Upload Quote Reply
drwho
Member
 

Joined: Fri Feb 8th, 2008
Location:  
Posts: 101
Status: 
Offline
the same boat indeed...
do appreciate it Markus
which reminds me to get some of that artisan mustard in your home town :)

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 9th, 2017 10:43 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Indeed. The shop is not far. Right now I smell the roasting of the coffee makers. Its practically next door to the mustard shop. Perhaps a good idea to forget about XP hassle and do a break.

Btw: I asked R&D to jump into conversation if something I said regarding VCL and XP is wrong.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 09:56 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > huge performance penalty in windows XP



WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize