Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
  • Welcome
  • Products
  • Support
  • About
  • More
  • Cancel
AssetWise Enterprise Interoperability
  • Product Communities
  • AssetWise
  • AssetWise Enterprise Interoperability
  • Cancel
AssetWise Enterprise Interoperability
AssetWise Enterprise Interoperability Wiki SEQ Memory Usage
    • Sign In
    • -Interop Overview (AssetWise Home)
      • +AssetWise and CMMS integrations - overview
      • +AssetWise Products and Adapters
      • -Service bus - enterprise message delivery
        • Configure email notifications of Dead Letters
        • Create a debug Message Archive
        • In RabbitMQ, preview a BOD message
        • +On premise RabbitMQ
        • Pausing message consumption in service bus
        • Reaching Swagger
        • +Reviewing cloud tenants
        • -SEQ Logging
          • Accessing SEQ Logs for Hosted Implementations
          • Configuring APM logging to use SEQ
          • Configuring retention policy for Seq logging
          • Exporting on-prem SEQ logs
          • SEQ Memory Usage
          • SEQ message size limits
          • Telling Seq not to use up the C drive
          • Troubleshooting tips for hosted Seq logs
          • Troubleshooting Using SEQ Logs
        • +Service bus explorer - Interop CONNECT edition
        • +Simulate posting a message to service bus
        • Tenant configuration user interface
        • Turn on Service Bus Debug logging - On Premise
    • Asset Reliability features with Interop
    • +Troubleshooting Interop with AssetWise
    • +Release Documentation

    You are currently reviewing an older revision of this page.

    • History View current version

    SEQ Memory Usage

    By default, SEQ will use as much memory as possible (90%) to cache log messages.  This is fine, if it's on a standalone server.

    If SEQ is installed on a shared server (e.g. on the same machine / VM as the Interop Service, or RabbitMQ) then it is important to limit the amount of memory SEQ will use.  

    to change this, open the config file located at %programdata%\seq\seq.json and change the SystemRamTarget to something lower, e.g. 0.2 meaning 20%:

    The tradeoff is that when older messages are flushed out of memory and the disk has to be accessed searching for older messages becomes quite slow.

    Troubleshooting: Memory usage always at 90% or above? It's probably this SEQ setting.

    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies