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.


 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius  
AuthorPost
bikedude
Member
 

Joined: Thu Aug 20th, 2009
Location:  
Posts: 118
Status: 
Offline
Building our product takes about 15 minutes. Ten is spent running slmake create.

We have tried every trick in the book. More CPU cores, SSD, more memory, more everything, but slmake does not budge.

I would like to see a more threaded slmake. It invokes msbuild and msbuild has options for running in parallel. Can something be done there?

danypd69
Member
 

Joined: Fri May 5th, 2017
Location:  
Posts: 6
Status: 
Offline
I have this problem too and I'm localizing in just 2 languages, I will have to add more languages and I'd like the process to be a little faster. My current build takes about 7 minutes only for slmake step.

ngallimore
Member
 

Joined: Wed Nov 11th, 2009
Location: Brisbane, Australia
Posts: 27
Status: 
Offline
+1 to this. One of our products that I've been trying to cut down on build time lately takes 17 minutes end-to-end. Nearly 7 minutes are spent running Sisulizer.

We've got 5 languages being generated and there are multiple C# projects in the solution.

Given that the output from Sisulizer of each Visual Studio project is independent and each output language is independent, this seems like a great opportunity for running things in parallel in order to speed up the overall time.



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

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize