We help IT Professionals succeed at work.

Tree View  loading - Document management system

Afternoon all,
        We have a client with a document management system that has a plug-in to the Microsoft office applications. Historically all data was saved on a central File server over a VPN hosted in a data center. The file server was 2008 (with SBS2011) originally. We have migrated the infrastructure to the Azure cloud with the following configuration:

Client -FP-02

All files are now stored on the FP-02 server ( all servers are 2012 R2, default image), this server is running at 5-10% CPU and 25-30% memory and so does not seem under stress. Local to Azure Ping is in the region of 10ms for latency.

Users on the local client machines use the office application (word/excel/outlook) for the day to day work. When saving a document they select a Doc Management tab on the office application top ribbon, inside they have an option to "Save As" when selected a popup screen opens listing all the mapped drives for the computer and when selected provide a Tree view of the folder structure contained inside. When selecting one of the bigger drive locations (14Gb) the file structure takes between 10 and 15 seconds to load/populate (each time). When navigated the correct location the save function again takes between 10-15 seconds to complete. When navigating using explorer via mapped drives the speed is as expected and the folder structure opens/closes as if the files were local.

I have installed the Windows Search feature on the file server in an attempt to speed anything up in the background (Indexing), could there be changes between the historical 2008 and the new 2012 that the DMS application need to take into account OR are there any settings within the new 2012 file server that can be enable to improve the saving/navigation speeds. Any suggestions you can offer would be much appreciated.
Watch Question

Distinguished Expert 2018
Azure's storage is designed for reliability, but that comes at a small performance cost. As such, what you describe is not exactly out of expectations. Azure does have higher priced performance storage that could improve your situation.


My Confusion on speed is when the DMS is placed in comparison with the File Explorer for navigating folders the process moves as expected with nice and fast navigation. I am wondering if the DMS is completing fresh indexing searches on the target shares, could this be causing the delays?
Distinguished Expert 2018
It certainly could be. But it is (from my end) also purely conjecture. This DMS is, so far, not named, and it may be a DMS I'm familiar with so even if you named it, I may mot be able to accurately say how it behaves or how to fix it. If I were troubleshooting, I'd be turning on performance counters and maybe even do some network captures to look for delays there. Delays in DNS, SMB, etc. But without identifying the cause, it is tough to propose a solution.


Sorry for the delayed response.

I have now found out that the application was written in 2006 using VB, would there be anything running on the historical servers that would have complimented the system and helped pull this information to the client machine when the tree view is called?

An extract from the application developer is as follows:

On load defaults to N: in the treeview
On any hyperlink:
                Resets the treeview
                Populates combo boxes
                Builds treeview for the selected drive
                Iterates through the folders in the treeview *

* We can’t speed up this process through indexing, as the treeview control does not support indexing. (The data source control doesn’t exist in VBA as it does in VB6).  Therefore it cant create a collection of all the nodes and purge in once instance, instead it has to loop in iterations.
The developer reworked the application to use a different explorer view


This required developer work and was outside of the infrastructure