Uniface 10.4 Compilation Performance

Hi,

We're seeing long compile times in our Uniface 10.4 development environment, with more complex components taking upwards of 90 to 120 seconds to compile each time. Though we've never had super quick compilation under Uniface 10, in particular, this does seem to have got worse, though I'm not really sure what would be considered a "normal" compile time.

Has anyone else seen something similar, or have any ideas what might be contributing (or what to look in to)? We're running patch 10.4.01.019, if that makes any difference.

Thanks,

David

Hi David,

Where exactly do you see the long compile times? Is this when compiling from the command line or within the IDE?

In case it is the latter then the setting $MESSAGE_LEVEL can certainly have an impact on performance. When using the value 0 ("Display error, warning, and information messages. Equivalent to /inf") can generate a lot of compiler messages that need to be parsed before it can be shown in the Compiler Output tab. Using 1 (error & warning messages) or 2 (only error messages) should speed up the process. But this, of course, comes at a cost (less compiler info).

At this moment I am, however, not aware that Uniface 10.4 is any slower than a comparable patch level of version 10.3, or version 10.3 in general.

Thanks,
Daniel

Sadly the lower message level didn't seem to make any discernable difference to the compile times, so we'll have to continue with our investigations. I guess it's at least good to know that this isn't something that has been reported by others, which may suggest some kind of infrastructure/set-up problem on our end.

Thanks,

David

Thanks for the suggestion. Switching the CMI and *LST files over to be written to a local disk does make a massive difference, consistently halving the time it takes to complete, so it looks like we might be on to something there.

What we have noticed is that if we delete the CMI and *LST files prior to running the compilation, then writing them to a network drive also results in the same halved compile time. If we then compile again, with the files in existence, we see the much slow compilation times again (which doesn't occur if recompiling when writing to a local drive).

I think the issue we would have with writing to local drives would be that we have it set up so that all developer compilations write to that same network drive so that the list of modules/entries are present and up to date when another developer opens that same form in IDE later on.

If we switch to local drives then wouldn't developers need to re-compile the form each time they opened it, before they would see the up to date list of entries on the right-hand side of the IDE? If that's the case, that would be a significant usability issue for us I suspect.

Thanks,

David

Thanks for the info. Interesting to know.

Regarding the CMI files: indeed, in case the files are stored locally then a developer would need to compile a component first in order to get the up-to-date data in the Compiled Module Info tab on the right-hand side of the component editor.

But maybe it would be an option to do the compilation on a server (writing the CMI files "locally")? The developers then could access the up-to-date CMI files through a common share. At this moment there is no straight forward way to do this from the IDE. But you could create a Worksheet or user-defined menu that calls a remote service which does the compilation on the server. Just an idea. But I guess there is room for improvement here.

I hope this helps.

Daniel

Hi,

We're seeing long compile times in our Uniface 10.4 development environment, with more complex components taking upwards of 90 to 120 seconds to compile each time. Though we've never had super quick compilation under Uniface 10, in particular, this does seem to have got worse, though I'm not really sure what would be considered a "normal" compile time.

Has anyone else seen something similar, or have any ideas what might be contributing (or what to look in to)? We're running patch 10.4.01.019, if that makes any difference.

Thanks,

David

Hi David,

We've encountered similar issues in our Uniface 10.4 environment - especially with more complex components or those with heavy-use libraries and triggers. While 90 to 120 seconds does seem a bit on the higher end, it's unfortunately not unheard of, particularly when dealing with a large codebase or when running on certain network or hardware configurations.

A few things worth checking:

• Ensure your antivirus isn't scanning during compilation.
  
  

• Try compiling locally versus over the network to see if there's a significant time difference.
  
  

• Look at the size and complexity of the components - sometimes, simplifying includes or modularizing logic can help.
  
  

• Also, consider updating to the latest patch if available, as some compilation performance tweaks have been made over versions.
  
  

I know it's a different context, but it reminds me of how compiling complex submissions for something like CMI Level 2 Assignment Help can be frustratingly slow if your tools or environment aren't optimized. Sometimes the little background settings make a big difference!

Hope that helps a bit - would be great to hear if you find a workaround.

------------------------------
cmi assignment helper
Looking for Reliable CMI Level 2 Assignment Help
Rocket Software Forum Member
------------------------------