You are viewing limited content. For full access, please sign in.

Question

Question

LF log analysis

Laserfiche
Updated August 4, 2016
asked on August 3, 2016

Hi,

We are having some performance issues in one LF Server based in HK but not in another server based in NL with the same LF version.

We parsed the logs for lf-LF.exe-LFSO92.dll and found that one particular operation is taking much longer in HK than in NL. 

XREPORT:

NL average duration  :  28

NL Standard Deviation:  93

 

HK average duration  :  89

HK Standard Deviation: 484

 

My questions:

  1. What is this XREPORT operation and if it is consuming a particular type of resource (e.g. diskIO, CPU, is it chatty over the network or has a long SQL Query?).

 

Thank you
Gian

 

 

 

0 0

Answer

SELECTED ANSWER
replied on August 4, 2016

The SQL query is built dynamically and it differs based on the version of the LF server. Your best bet for tracking down the problem is to monitor the SQL server itself. You can use the SQL profiler to see the queries that are run. Check out this presentation on database performance that might be useful.

To understand the logs better, look at the url for each XREPORT to tell what kind of report it is. /+LF/entry/<id> is retrieving information for a single entry. /+LF/entry/<id>?continuationguid=<guid> is retrieving an entry listing. /+LF/search/result/<guid> is retrieving search results.

0 0

Replies

replied on August 3, 2016

XREPORT is use for a variety of retrieval operations including folder listings, search results, entry info, page info, and some other administrative information. The slowest of these is probably retrieving entry listings, which performs a SQL query for the contents of a folder.

0 0
replied on August 4, 2016

Thank you Robert,

Can we have the SQL query run for the retrieving entry listings?

Also, is there any way to find in the trace log exactly what kind of XREPORT operation is being done? If it is a search or a folder listing, etc.

Thank you
Gian

0 0
SELECTED ANSWER
replied on August 4, 2016

The SQL query is built dynamically and it differs based on the version of the LF server. Your best bet for tracking down the problem is to monitor the SQL server itself. You can use the SQL profiler to see the queries that are run. Check out this presentation on database performance that might be useful.

To understand the logs better, look at the url for each XREPORT to tell what kind of report it is. /+LF/entry/<id> is retrieving information for a single entry. /+LF/entry/<id>?continuationguid=<guid> is retrieving an entry listing. /+LF/search/result/<guid> is retrieving search results.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...