Hallo!
Da dies mein erster Beitrag ist stelle ich mich kurz vor: Mein Name ist Kai, ich komme aus NRW und arbeite seit über 20 Jahren mit VO. Bis heute bearbeite und pflege ich nach wie vor mit VO einige größere Projekte. Die Umstellung auf Vulcan war schon 2014 geplant wofür ich ein Projekt portiert habe, was auch mit nur wenigen Problemen fehlerfrei geklappt hat. Was schon bei Vulcan auffiel und jetzt bei X# auffällt ist, dass der Compiler gefühlt ewig läuft bis die .exe erzeugt wurde. Was bei VO in Sekunden erledigt ist braucht in C# bei einem meiner Projekte über 25 Minuten, und das nur für die .exe, diverse DLLs noch gar nicht mitgerechnet. Das macht natürlich jeden wirtschaftlichen Einsatz von Anfang an undenkbar und wird besonders ärgerlich wenn man dieses oder jenes ausprobieren möchte, man sich mit der Suche nach Fehlern rumplagen muss oder schlicht einfachste Tippfehler eingebaut hat.
Daher die Frage: Gibt es eine Möglichkeit die elendig langen Compilierzeiten zu reduzieren oder wie handhabt ihr das Problem?
Gruß
Kai
Compiler Laufzeit
Moderator: wriedmann
Compiler Laufzeit
Hallo Kai,
so lange sollte kein Compiler-Lauf dauern.....
VO arbeitet komplett anders als X#/C#/Vulcan.Net: es werden immer nur die geänderten Entities kompiliert, daher geht das sehr schnell.
Wie groß ist denn Deine Exe, bzw. wie viel Quellcode steckt da drin?
Normalerweise sollte eine Modularisierung die Lösung bringen, aber ich denke, da läuft irgendwas schief.
Und noch was: der Compiler der Community-Version ist meines Wissens nach etwas langsamer, da er Debug-Code enthält.
Wolfgang
so lange sollte kein Compiler-Lauf dauern.....
VO arbeitet komplett anders als X#/C#/Vulcan.Net: es werden immer nur die geänderten Entities kompiliert, daher geht das sehr schnell.
Wie groß ist denn Deine Exe, bzw. wie viel Quellcode steckt da drin?
Normalerweise sollte eine Modularisierung die Lösung bringen, aber ich denke, da läuft irgendwas schief.
Und noch was: der Compiler der Community-Version ist meines Wissens nach etwas langsamer, da er Debug-Code enthält.
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Compiler Laufzeit
Kai,
25 minutes is unacceptable.
What is the size of your app? (lines of code, modules etc)
What are the specs of your computer ?
Robert
25 minutes is unacceptable.
What is the size of your app? (lines of code, modules etc)
What are the specs of your computer ?
Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
The Netherlands
robert@xsharp.eu
Compiler Laufzeit
Hello,
Compiling 1 change in the project we are converting takes about a minute. If VO invalidates multiple libraries and the main program(s) using them, due to a change in a commonly used library, I can have it compiled and re-running in <10 seconds which is less than just restarting a .Net based program. Not only X#, also C#.
So the progress of .Net has brought us half an hour or more waiting time a day instead of a few minutes a day like in VO.
Dick
Compiling 1 change in the project we are converting takes about a minute. If VO invalidates multiple libraries and the main program(s) using them, due to a change in a commonly used library, I can have it compiled and re-running in <10 seconds which is less than just restarting a .Net based program. Not only X#, also C#.
So the progress of .Net has brought us half an hour or more waiting time a day instead of a few minutes a day like in VO.
Dick
Compiler Laufzeit
Robert,
Just to be clear, I think Kai mentioned that this delay is with a c# program, not with X#. Still indeed unacceptable, but I'm guessing there something very special about it.robert wrote: 25 minutes is unacceptable.
What is the size of your app? (lines of code, modules etc)
What are the specs of your computer ?
Chris Pyrgas
XSharp Development Team
chris(at)xsharp.eu
XSharp Development Team
chris(at)xsharp.eu
Compiler Laufzeit
Hello!
The .exe-file which was generated by C# has a size of 6442 KB.
The .exe file which was generated by VO has a Size of 32660 KB
The VO-AEF-File has a Size of 25727 KB
Additionally some dll files are used which in total have a size of 5500 KB (generated by C#).
The VO-AEF-File contains 17200 Entities for the .exe file and the AEF-Files for the DLLs contain totaly 16250 Entities.
I use a normal PC with a Intel core I5 processor, 8 Gig RAM and SSD-Harddisc. The complete compilation of the whole Project including all DLL-Files with VO takes less than 4 Minutes.
The .exe-file which was generated by C# has a size of 6442 KB.
The .exe file which was generated by VO has a Size of 32660 KB
The VO-AEF-File has a Size of 25727 KB
Additionally some dll files are used which in total have a size of 5500 KB (generated by C#).
The VO-AEF-File contains 17200 Entities for the .exe file and the AEF-Files for the DLLs contain totaly 16250 Entities.
I use a normal PC with a Intel core I5 processor, 8 Gig RAM and SSD-Harddisc. The complete compilation of the whole Project including all DLL-Files with VO takes less than 4 Minutes.
Compiler Laufzeit
Hi Kai,
C# or X#?
If C#: how do you have moved VO code over to C#?
Wolfgang
C# or X#?
If C#: how do you have moved VO code over to C#?
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Compiler Laufzeit
Hi Wolfgang.
Sorry, X# of course.
I used the X# VOExporter from the XIDE (Help -> X# -> Run VOExporter)
Sorry, X# of course.
I used the X# VOExporter from the XIDE (Help -> X# -> Run VOExporter)
Compiler Laufzeit
Hi Kai,
since you have written "C#" for more than one time, I preferred to ask.
Of course, this compile time is too long.
Maybe 8 GB of memory may be a bit small - dou you are using XIDE or Visual Studio?
And when you look at the taskmanager: your memory is full with other applications?
Do you have all your code on your local SSD?
And what X# version do you are using?
Wolfgang
since you have written "C#" for more than one time, I preferred to ask.
Of course, this compile time is too long.
Maybe 8 GB of memory may be a bit small - dou you are using XIDE or Visual Studio?
And when you look at the taskmanager: your memory is full with other applications?
Do you have all your code on your local SSD?
And what X# version do you are using?
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Compiler Laufzeit
Hi Wolfgang!
I'm using XIDE. All Code is on the local SSD. I'm using Version 2.9a. I downloaded it just a few Weeks ago because since my Vulcan test I lost Interest on migration of the VO-Code to the .net world because Vulcan was also significantly slower than VO. But now I have some tasks to solve that would be easier to solve with the .net framework.
Maybe 8 GB is to small, but I have never 100% memory usage during compilation. In most cases memory usage is around 90 percent.
Kai
I'm using XIDE. All Code is on the local SSD. I'm using Version 2.9a. I downloaded it just a few Weeks ago because since my Vulcan test I lost Interest on migration of the VO-Code to the .net world because Vulcan was also significantly slower than VO. But now I have some tasks to solve that would be easier to solve with the .net framework.
Maybe 8 GB is to small, but I have never 100% memory usage during compilation. In most cases memory usage is around 90 percent.
Kai