Versions Compared
| Version | Old Version 5 | New Version Current |
|---|---|---|
| Changes made by | ||
| Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
...
The hardware configuration that NLINK runs under can affect its performance for better or worse. For details on the minimum hardware requirements see “NLINK Hardware Requrements”. If your hardware does not meet at least the minimum requirements needed by NLINK, you should consider upgrading the hardware before addressing any performance issues
Performance monitoring
Microsoft Windows Operating Systems (2008, 2012 R2) comes with a tool called “Performance Monitor”. Performance Monitor can be used to monitor the NLINK Server. See How to Collect Performance Statistics for tips on configuring Performance Monitor. Make sure the sampling rate is set properly so that a long duration of data is captured (over hours or days rathers than minutes or seconds).
...
- Interface Log files
Using the NLINK Log Message Action, data specific to an Interface can be written to Interface Log files. These files can contain information relevant to specific Interface. If the meta-database is configured to generate Interface Logs then make sure there is enough information in the messages to capture the key issues. These files will be different for each NLINK installation since they are purely configuration-driven.
- NLINK Logsand Logs and Trace files
NLINK CoNNectors and eXtenders can generate traces of all their activity. These traces along with Event Log can provide insight into all the activity in NLINK. Some of the contents of Trace files might be useful only to Junot Systems support.Use the NLINK Management Module (NMM) to activate the NLINK traces. The screen is under the Tools >> Settings menu option. Click on the Advanced Options tab to get to the Activate NLINK Server Trace flag. These trace files are different than those generated using NLINK System Properties Debug Level and Create Dump File.
...
Various metrics gathered from Performance Monitor can be used to see where maximum resources and time are being spent and understand bottlenecks in systems.
A low number (over a long period of time) will indicate that application(s) are starved for memory. Adding If this value is less than 5 percent of the total physical RAM, that means there is insufficient memory, and that can increase paging activity. Adding more physical memory (RAM) might help performance or moving some applications to another box might also be a factor to consider.
Page Faults / Second
The page faults / second counter indicates the frequency of hardware page faults--pages which had to be retrieved from hard disk since they were not in working memory. In a typical system there will be some page faults but this should be a low number. A large number of page faults/sec indicates excessive paging.
Virtual Bytes
At some point after startup, once all the interfaces reach steady state, the NLINK virtual bytes will fluctuate within a certain range. The period of time the NLINK Server needs to reach steady state will vary in each deployment. The important thing is that the virtual bytes should not increase forever. The practical limit for NLINK virtual bytes is 3 GB on 64-bit Windows, or 2 GB in 32-bit Windows with /3GB switch, or 1.5 GB in 32-bit Windows.
If NLINK's virtual bytes value is consistently increasing, it probably indicates some sort of memory resource issue, which will require further analysis.
Similar to virtual bytes, private bytes should reach a steady state value and then should fluctuate within a certain range. The practical limit for NLINK private bytes is 2.5 GB on 64-bit Windows, or 1.5 GB in 32-bit Windows with /3GB switch, or 1 GB in 32-bit Windows.
If NLINK's private bytes value is consistently increasing, it probably indicates some sort of memory resource issue, which will require further analysis.
Processor Time
Processor time can provide a rough indication of throughput and help identify potential issues. if the ”Processor Time” for NLINK is a fraction of the overall time taken to run an Interace, then you should focus on monitoring the other External Systems (e.g. SAP, SQL Server or any other system NLINK needs to interact with) to get a better understanding of the throughput issues.
Disk space
Typical NLINK operation requires about 1 GB of free disk space. In most cases NLINK configuration files take up less than 30 MB. The rest of the disk space requirement depends on the use of advanced features, such as Store and Forward and the amount of logging configured in meta-database.
Most run time logs that NLINK generates can be cleared periodically or backed up to a secondary server as needed. The NLINK trace file 'NLINK.trc" cannot be deleted or moved when NLINK is running.