• Replies 1 reply
  • Subscribers 583 subscribers
  • Views 120 views
  • Users 0 members are here
Options
Related

OFSOPC Disk Device

Ignatius

I was wondering if someone could explain why we would use OFSOPC as a disk device [RUN]:Test.dsk but then set the memory mode to true in the device setup. This is used extensively in the example project. what is the implication of this configuration?

Parents
  • Hi Ignatius,

    There is a subtle difference. See this note in the help:

    "Note: With the release of version 7.20, a feature called persistence could be applied to I/O devices in memory mode. Using a Persisted Memory I/O device is recommended as an alternative to using a disk I/O device, as full synchronization is supported if a server becomes unavailable for a period of time. See Persisted I/O Memory Mode for more information."

    In the Example project in 2018 (and the up and coming 2018 R2 release) the configuration has been cleaned up to be pure memory I/O Devices with persistence enabled. You will not find any Disk devices in the Example project anymore.

    It is recommended you use persistence memory mode going forward.
Reply
  • Hi Ignatius,

    There is a subtle difference. See this note in the help:

    "Note: With the release of version 7.20, a feature called persistence could be applied to I/O devices in memory mode. Using a Persisted Memory I/O device is recommended as an alternative to using a disk I/O device, as full synchronization is supported if a server becomes unavailable for a period of time. See Persisted I/O Memory Mode for more information."

    In the Example project in 2018 (and the up and coming 2018 R2 release) the configuration has been cleaned up to be pure memory I/O Devices with persistence enabled. You will not find any Disk devices in the Example project anymore.

    It is recommended you use persistence memory mode going forward.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.