Optimising Performance of Uniface with UD6

UD6/CMtool driver is a designed for storing your Uniface source repository and using the IDF quickly and efficiently.

We have many customers using UD6 with Uniface 6, 7, 8 and Uniface 9 - in large and small teams, with Unix servers and also with Windows Desktops, using a variety of change control methodologies and tools - and performance is great at most installations. If you have a performance problem - contact us because these problems can almost always be solved after some diagnostic processes.

For many people trying UD6 for the first time the performance is adequate. Regardless of if the performance is OK or clearly needs improving - the performance can probably be improved by checking several settings and talking to our technical support team. A single page in a help file is not going to resolve every issue - please do contact support@march-hare.com if you have persistent performance issues so our team can help you.

What affects the performance

UD6 performance is affected by many things:.

• Disk storing the UD6 XML files (eg: NTFS vs FAT, Local vs. Network, SAN vs. NAS, SCSI vs IDE.
• Anti-virus software settings.
• Clustering.
  • is ULANA clustered with Components/Model.
  • is the 'new' UCRELSH setting in use (default is on)
  • is USTEMP and other 'binary' data stored in UD6 XML format or ISAM or a SQL database
• Is 'auto-retrieve' disabled in IDF User Preferences screen?

Clustering

This help file contains a page on Clustering: What is stored where in UD6. The clustering options chosen 'by default' are a balance between 'usability' and 'performance', ie: the default is not the best performing. To discuss you clustering requirements and the effect on performance please talk to our support team via support@march-hare.com

Anti-Virus Software Settings

The most common cause of poor performance is the configuration of anti-virus software on windows. The XML files can never contain a virus - they are not executable files, therefore it is never sensible to scan them for viruses. UD6 can read thousands of XML files every second - but this rate can drop to 100's or even fewer when some anti-virus systems attempt to scan every file every time it is accessed.

Disk storing UD6 XML files

For the best performance store your UD6 XML files on a locally attached SCSI disk with a battery backed write cache. The worst performance will be obtained by using a 'NAS' or a 'Network Share'.

Auto Retrieve

The IDF user preferences can be used to turn off 'auto retrieve' on browse screens like the 'open component' form. If your repository contains several thousand components then you are unlikely to scroll through the list to find and open the one you want. Creating and populating that list takes UD6 time that is then wasted if you just 'clear' that form. It is best to turn off 'Auto Retrieve' and then the 'open component' screen will appear instantly.

•  1. UD6 Overview
•  2. Basic Theory of Configuration Management
•  3. Configuration Management applied to Uniface
•  4. Comparison: VC-Link (PVCS-Uniface Bridge)
•  5. Comparison: Uniface 8 (SCCI Bridge)
•  6. Clustering: What is stored where in UD6
•  7. NLS Support Overview
•  8. UD6 Option Pack
•  9. System Requirements
•  10 UD6 Article Links
•  11 Uniface 8 Migration
•  12 XMLGREP Search and Replace
•  14 MAKE Build Management
•  15. UD6IDE: Eclipse editor for Uniface 6, 7, 8 and 9
•  16. theu.info - You in Uniface

1.2 2013/09/24 06:43:55

[go to top]