Skip to main content
Version: 3024.3

Fusion File Share Maximum Values

Many customers want a better understanding of the maximum supported values and theoretical limits of Fusion File Share.
Please refer to section 8 of the Fusion File Share manual for more information on optimizing performance.

How many shares can Fusion support?

Fusion does not limit the number of shares. Fusion is configured to allow registering 4294967295 shares.

Memory and CPU considerations

Fusion allocates a certain amount of memory to hold share information for every registered share. You can monitor the amount of memory allocated for the share object by observing the memory usage of the respective process.

Your Fusion configuration options determine the number of threads that are allocated for each registered share. The number of logical cores/processors available will be the number of threads that Fusion can run concurrently. So, two logical cores will allow two threads to run concurrently.

The number of shares is only limited by how many threads the Fusion process is allowed to start and the amount of memory available for allocating a new share object.

What are the impacts of a large number of shares?

With a large number of shares, a SMB client may have a very slight delay when first connecting to a share since the lookup operation for a particular share will take longer. However, this delay shouldn’t be very high and will probably not be noticeable.

How many client connections can Fusion support?

Fusion's limit on the number of client connections is limited by one or more of the following factors:

  1. The maximum size of the counter tracking the total number of clients
  2. The maximum allowed connections set in the configuration file
  3. Available memory for storing information related to the new client object

More clients translate to more sessions, tree connects and transport objects. When a message is received from a new client, it is necessary to verify the authenticity of the request and this requires looking up session, tree-connect and connection associated with the request. Fusion optimizes this process even with a huge number of client connections to prevent delays. In testing Fusion easily supports 200 new client connections per second.