Question

Best practice folder limit?

Laserfiche

Updated November 21, 2019

asked on November 20, 2019

I have a Laserfiche sandbox repository where I am testing folders for Municipal Properties. We have about 13k Parcels. My focus to this point has not been performance of the repository as I have been occupied with automating creating the folders and adding basic metadata.

The Laserfiche repository in the thick client has no trouble working with the 13k property folders at the "root", but the web client is choking on it.

As I think more about this it's probably a bad idea to have 13k folders in the root and that I should break them up in to smaller, more manageable sub folders. I am curious at this point though if I have a pending issue with the configuration of my server. Should the web client be able to present 13k folders to the user?

0 0

Answer

SELECTED ANSWER

replied on November 20, 2019

I would say that 13K is probably more items than you want in a single folder. Another thing to take into consideration is the number of columns displayed.

In my experience, the desktop client choked on larger folders more than the web client because the web client only really loads "chunks" and updates what is displayed when you scroll; this is common because browsers can only handle so much data.

If your folder view is showing a lot of columns with metadata, then it has to retrieve all of that when you open the folder, so more columns = slower loading. As a result, it could be a compound issue.

So, I'd look at the following:

How many columns are being displayed in each client
Do you see any spikes on the server when you load the web client
Is it actually the web client loading slowly, or is it the browser running slow

At the end of the day, I would highly recommend sub folders anyway. Even if you maximize performance, sorting/scrolling through 13K entries is much more of a hassle than just having categorized sub folders.

2 0

Replies

replied on November 20, 2019

Makes sense. My focus has been getting the folders created through a workflow. I am not sure why I thought 13k folders in one place was a good idea. There is a logical definition I can use within the parcels that will keep them in 40 or so primary folders which would put 200-400 parcels in each of those folders. Much more manageable.

1 0

replied on November 21, 2019

We had to do a split with our bylaw enforcement files which were addressed based. We found 2400 froze the browser. I think after 1000 files things start to hang. I’d recommend no more than 1000 entries a folder.

1 0

You are not allowed to follow up in this post.

Question

Question

Best practice folder limit?

Answer

Replies

Sign in to reply to this post.