Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Slow response in TWO_TASK caused by distance between App server <-> Firewall <-> DB server

    Slow response in TWO_TASK caused by distance between App server <-> Firewall <-> DB server

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Description
    2. Resolution

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

    Description

    After moving to or changing a TWO_TASK server setup, I/O intensive functions, such as indexing jobs, take longer than they did previously. 

    Resolution

    In at least one case, this slowness was caused by the fact that each communication between the App and DB servers (which were less than 1m apart) was going through a firewall, which was 35km away (70km, round-trip), which was slowing them down.  Pings were taking an average of 2.8 ms -- while 0.7ms was the normal, expected latency.

     


    • Article last edited: 30-Mar-2016
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Slow response in RESTful API when patrons have many loans
      • Slow response time accessing item records in GUI
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. firewall
      2. latency
      3. TWO_TASK
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved