Automatic upload/download speed optimization

Introduced in v4.2, there’s a registry setting that allows Server! to automatically choose the socket’s inbound and outbound buffer sizes in an attempt to optimize upload and download speeds.

This setting cannot be configured in the web interface, the only way to set it is at Windows registry level. Restarting the Server! system services is not necessary, as this setting is pulled from the registry every time a new incoming connection is served. Continue reading

How to increase the speed of SFTP downloads Server! version: 3.0.0+

If you run Server! hosted on a VM in the cloud or at some co-location provider, you are probably aware that your ISP uses traffic shapers to optimize the transfer speed and to prevent malicious users from abusing network resources.

In some cases, though, such strategy (packet/traffic shaping) clashes against the very nature of the SSH/SFTP protocol, in which both control and data packets are sent on the same connection. In particular, you may experience issues between the requested SSH socket buffer and the advertised buffer size on the network. If that happens, we got you covered! As of version 4.0, in fact, you can use a special Registry key to force Server! to use a socket buffer size that matches the one advertised by your network. Continue reading

Maintenance release: Server! v3.1.17.57

We have just released version of our Server!

This new maintenance release fixes a bug in the global speed limit configuration. Under certain circumstances, in fact, only user-specific speed limits were enforced, while global speed limits were ignored; now it’s fixed.

As usual you can download the latest version from our web site. Thank you! Server! v4: high speed and savvy RAM usage

This article refers to Server! v4.0, which – at the time the article is being written – is still in beta, and is not yet available for purchase by customers. The purpose of this article is to inform our users about some important upcoming features.

The development team is running some final tests on the core engine of the upcoming Server! v4, and we’re witnessing amazing results.

Long story short, the brand new core engine of version 4.0 is not only much (much!!) faster than any previous version, but it uses on average half of the RAM! See the following screenshot of the Task Manager taken from one of our test systems: Continue reading Server! v3.0: more on speed limits…

As we already mentioned in a previous post, Server! v3.0 will feature a very granular configuration regarding speed limits. This post explains how such limits work in detail.

First of all the are 2 lists of limits: a global list that refers to the whole server (regardless of the user who is connecting) and a second list that is defined in the user profile, and only affects that specific user.

Second, and most important, it is essential to understand that the speed limit list defined on a specific user, always prevails over the global one.

So let’s assume, for example, that the following limits are defined globally:

And the following limits are defined specifically for the user johndoe:

When the user johndoe connects from the local area network (192.168.X.X) he will have an upload/download speed limit of 1024 KB/s, as set in his own profile, regardless of what the global configuration limit is for the same network; the user configuration always supersedes the server’s global/default configuration. Server! v3.0 will feature speed limits

Just a quick note to let our users know that our dev-team has just finished implementing speed limits in Server! v3.0. Tested. It runs smoothly.

Speed limits can be configured globally (server-wide, per instance) as well as individually for each user, and the upload and download speed limits can be specified separately.

Here you can see a file transfer with the speed limit disabled. This test was performed on a 100 Mbps LAN, and as you can see the upload speed is 12.95 MB/s (103.6 Mbps, with compression, LAN bandwidth is saturated).


Now, this is the same test, but with speed limit enabled. As you can see, the upload only takes up to the allocated bandwidth and does not saturate the LAN.


Speed limits can be configured globally, per user, or per network. Therefore you can have different speed limits applied to the same user depending on the IP address he/she is connecting from.