Versions Compared
| Version | Old Version 3 | New Version 4 |
|---|---|---|
| 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 minimum hardware requirements see “NLINK Hardware Requrements”. If your hardware does not meet at least minimum requirements needed by NLINK, you should consider upgrading hardware before addressing any performance issues
Performance monitoring
...
Event log size
NLINK Server uses the Windows Event log to report any issues/problems encountered at run time. Depending on the volume of information being captured, you will need to set the size of Event log accordingly, so that all the events that occur over the monitoring time are capured for analysis. Note that setting Event log to be too big makes it difficult to use. A good guideline would be to set it on the order of 100 MBs (not GBs).
The NLINK Event log in conjunction with “Performance Monitor” can be used to determine acitivity in NLINK.
Log and Trace Files
- 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.
- NLINK Logs and Trace files
NLINK 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 then those generated using NLINK System Properties Debug Level and Create Dump File.
| Note |
|---|
Any (or all) of these options can generate large volumes of data that can further slow the system down and impose further performance penalties. These flags should be used with caution and only used to troubleshoot for a limited period of time, and ideally never in a production environment. NLINK Server running in “debug” mode (with NLINK System Property Debug Level set to Debug) will not reflect a normal production environment. |
Related articles
| Filter by label (Content by label) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 more physical memory (RAM) might help performance or moving some applications to another box might also be a factor to consider.
Page Faults / Second
Page faults/ second counter indicates number 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 some low page fault count. Large number of page faults/sec indicates excessive paging.
Virtual Bytes
After certain point of time once all the interfaces reach steady state, the NLINK virtual bytes will fluctuate with in certain range. The period of the NLINK needs to reach steady state will vary by every deployment. Neither the virtual bytes should not increase forever. Practical limit for NLINK virtual bytes 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 most probably indicates some sort of memory resource issue, it will need further analysis to determine the cause.
Similar to virtual bytes, private bytes should reach a steady state value and can fluctuate between certain range. 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 most probably indicates some sort of memory resource issue, it will need further analysis to determine the cause.
Processor Time
Processor time can provide rough indication of throughput and help identify potential issue. if ”Processor Time” for NLINK is a fraction of the overall time taken to run an Interace, then the other External Systems (e.g. SAP, SQL Server or any other system NLINK needs to interact with) might need monitored to get a better understanding of the throughput issues.
Disk space
Typical NLINK operation will requires 1 GB of free disk space. In most cases NLINK configuration files can take up less than 30 MB. Rest of the disk space requirement depends on the use of advanced features, such as Store and Forward and amount of logging configured in meta-database.
Most run time logs generated can be cleared periodically or backed up to secondary server as needed. NLINK trace file 'NLINK.trc" cannot be deleted or moved when NLINK is running.