Syncplify.me Server! v4.0.34 released

We have just released version 4.0.34 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed: white-list rejection handling in the FTP(E/S) protocol handler (SFTP was not affected)
  • Improved: license persistence in complex virtual environment featuring partially dynamic virtual hardware (Warning: upgrading to 4.0.34 from any previous version will invalidate your license, so please if you are a customer – before you upgrade – contact us to request a license reset)

Note: if after the update you notice any unexpected behavior in the web interface, just hit Ctrl-F5 in your browser; that will force the browser to reload the page as well as all back-end scripts and update the ones that may have been cached from previous versions of the software.

As usual you can download this new release from our website.

New release: Syncplify.me FTP Script! v3.0.3.43

New major update for Syncplify.me FTP Script! Version 3.0 is finally here! And here’s a non comprehensive list of the main new features:

  • Multi-threaded parallel uploads and downloads
  • Configurable number of concurrent file transfer threads
  • Automatic keep-alive for lengthy operations
  • Automatic adjustment of file timestamps
  • Performance increase by up to 400%
  • Redesigned user interface for the script runner (execution environment)
  • More examples and ready-made templates

As usual you can download the new version from our web site. Thank you!

How many concurrent file transfer from the same client?

Sometimes our users ask us how many concurrent file transfers can be initiated simultaneously by one client. The answer deserves a little bit of explanation.

First of all it is important to understand that this article is entirely focused on how to optimize the client side, in fact the server uses I/O completion ports and RTL critical sections to optimize concurrency under heavy load (hundreds or thousands of incoming client connections) and is therefore self-optimized.

The client side, instead, is very different. First of all the client has a GUI (graphical user interface) that needs to be synchronized with the “desktop” of the operating system. Furthermore, on the client side, the concept of “CPU core affinity” becomes very relevant. What is it? Let’s try to provide a simplified explanation… Continue reading