Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Analysis of OPAC response time

    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23


    Aleph OPAC response time is slow. 


    Check the Oracle indexes for the Bib, ADM, and HOL libraries with the all_indexes SQL, as described in " How to tell if Oracle indexes for a particular library are present & VALID ".

    Check tab_base.lng for severe truncation, as described in the article " Logical base response very slow ".

    See if searches on common words with many hits take longer than other searches. If so, see article " Keyword searching on common words takes extremely long; multiple z97's "

    grep the OUT lines in the www_server_499n.log into a file grep.www.out (these include every time the OPAC user hits Enter):

    >grep OUT www_server_4991.log > wwwOUTgrep

    Then do greps  of this wwwOUTgrep file to analyze the numbers of transaction responses in specific time ranges (seconds):

    aleph@aio0001(a23_1):~/a23_1/log>grep -c 'OUT 0.' wwwOUTgrep
    aleph@aio0001(a23_1):~/a23_1/log>grep -c 'OUT 1.' wwwOUTgrep
    aleph@aio0001(a23_1):~/a23_1/log>grep -c 'OUT 2.' wwwOUTgrep
    aleph@aio0001(a23_1):~/a23_1/log>grep -c 'OUT 3.' wwwOUTgrep

    If greps show that almost all of the times are ten seconds or less and you are seeing much longer response times, it could be a communication issue.  Please consult the article  ELAPSED-TIME" in pc_server logs and actual response time  in this regard.

    See also articles:   

    Web OPAC and GUI Search keyword searches (Find), extremely slow / time out  

    Logical base response very slow 

    Keyword "Exact Title" searches time out and shut down the session



    • Article last edited: 13-Nov-2017