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

Question

Question

Our Laserfiche 9 application is unacceptable SLOW when run in our DMZ

asked on February 11, 2014

I created an application that uses the Laserfiche 9 .Net 4.0 Framework API to retrieve and then display PDF documents within a browser window.

 

When the application is run on our intranet web server, documents are displayed within about two seconds.

 

When the same application is run from our DMZ internet web server, documents take thirty to forty seconds to display which is about 20 times longer. There is a firewall between the DMZ internet web server and the Laserfiche application server. The application server lives within our intranet.

 

In an attempt to speed up Laserfiche response times, I tried to a fix that worked for Laserfiche 8.3. The fix didn't work for 9. The fix is to add a registry key:

 

1. Start regedit

2 . Expand HKEY_LOCAL_MACHINE.

3. Expand SOFTWARE.

4. Expand Laserfiche.

5. Expand Engine.

6. Expand 8.0.

7. Select the HttpServ key.

8. From the Edit menu, point to New and click DWORD Value.

9. Name the new value: ReverseNameLookup

11. Set the value of the new key to 0.

12. Restart the Laserfiche service

 

Your help in resolving this issue is greatly appreciated.

 

Timothy

 

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on February 11, 2014

Since disabling reverse name lookup didn't speed up your application, the most likely problem is that the firewall is introducing some latency into the traffic between your application and the server.  There are a few things you can try to troubleshoot this.

 

If you turn on RA tracing (via Laserfiche.RepositoryAccess.MethodTracer.InitializeMethodTracer) you'll get a log of your application's communication with LFS.  You'll want to see if the log shows a general slowdown or if there is one particular call that takes a long time.  Either way, you'll need to work with your IT staff to resolve it.  You might take a packet capture on both the LFS machine and your server in the DMZ.  Something you might experiment with is turning on SSL for the connection to LFS.  If the firewall can't inspect the data, it might forward them more quickly.

0 0
replied on February 11, 2014

Thanks Brian. I have passed your thoughts on to the Firewall people.

 

Timothy

0 0
replied on February 12, 2014

Actually, the RA tracing functionality is new in SDK 9.1, which hasn't been released quite yet.  Until you are able to upgrade you'll need to rely on tools like Wireshark or WinHttp tracing.

0 0

Replies

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

Sign in to reply to this post.