What are the memory limits for FactoryTalk Linx and how can I optimize its usage?

In the
Windows
 Resource Monitor, you can monitor
FactoryTalk Linx
's memory usage by observing
FactoryTalk Linx
 OPC Runtime Service
 and
FactoryTalk Linx
 Instance02 OPC Runtime Service
. But what is the maximum memory limit for
FactoryTalk Linx
?
Windows
 normally allocates up to 2GB of random-access memory (RAM) for a 32-bit application and 2GB for kernel drivers. So
FactoryTalk Linx
 is guaranteed at least 2GB of memory. To optimize performance, a compiler option is implemented that allows an application to use a portion of the kernel driver's memory allocation, typically providing an additional 1GB. This means
FactoryTalk Linx
 can generally use up to 3GB of memory.
FactoryTalk Linx
 uses memory for the following content:
  • Storing the tag definitions associated with shortcuts.
  • Managing the communications for tags requested by other
    FactoryTalk
     software.
  • Storing the Logix tag-based alarms.
If the memory usage of
FactoryTalk Linx
 exceeds 2.5GB, try the following options to optimize performance:
  • Optimize Tag Usage: Set the
    External Access
     attribute of unnecessary controller tags to
    None
     in
    Studio 5000 Logix Designer
    .
  • Distribute Workload: Shift controller shortcuts to a different
    FactoryTalk Linx
     instance or server in
    FactoryTalk Administration Console
    .
TIP: Starting with
FactoryTalk
 Services version 6.50.00, the
FactoryTalk
 Resource and Status service can be configured to monitor specific services and report the resource usage. Select
RSLinxNG.exe
 for the
FactoryTalk Linx
 Instance01 Service or
RSLinxNG02.EXE
 for the
FactoryTalk Linx
 Instance02 Service to obtain a dynamically updated tag for the memory usage of these services. This data value can be incorporated onto an HMI screen or trigger a
FactoryTalk
 alarm.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal