Title
 Overview
 Features
Setup
 

Choosing a Package

Connectivity

Install Windows

Install macOS

Install Others

License Codes

Adding Users

Performance

servedat Server
 

Access

Users

Home Directories

Access Privileges

SysAuth

AuthFile

AuthHandler

mkpasswd

Features

Host Groups

Encryption

Compression

Upload Status

Capacity

Monitoring

Logging

Object Handlers

Structured Lists

Configuration

Configuration File

Negotiation

Options

Web Integration
 

Web Clients

expedat:// URLs

JavaScript API

HTTP API

WebDat Ref UI

Server Dashboard

Landing Page

Web File Browser

Desktop Client
 

Basics

Interface

Authentication

Browsing

Getting

Sending

Copying Folders

Canceling

Resuming

Errors

Advanced

Encryption

Compression

Automatic Retry

Multitasking

Web Integration

Object Handlers

Branding

Maintenance

Renaming Files

Deleting Files

New Folders

Name Filters

Configuration

About

Options Window

Settings

Embedding

Priority

movedat Client
 

Basics

Browsing

Getting

Sending

Copying Folders

Authentication

Canceling

Resuming

Advanced

Encryption

Compression

Displaying Files

Path Completion

Maintenance

Renaming Files

Deleting Files

New Folders

Automation

Automatic Retry

Wildcards

Filters

Object Handlers

Piping Files

Logging

Structured Lists

Reference

Errors

Exit Codes

Configuration File

Options

DropDat
 

Creating Droplets

Changing Droplets

Sending Files

Pause & Abort

Automatic Retry

Distribution

Filters

Command Line

Limitations

Mobile Client
 

Adding Servers

Sending Files

History

Limitations

WebDat
 

Installation

Status Menu

Selection Dialogs

mtping Utility
 

Servedat Status

Latency

Load Monitoring

Route Tracing

Response Output

Transaction Report

Option Summary

Support
 

Revision Codes

Known Issues

Troubleshooting

 Legal Notices

Compression

Certain data types, such as text documents, may transfer faster if the data is compressed while in transit.  ExpeDat can apply ZLIB compression to transferring files, which typically reduces the size of compressible data types to about one-third of their original size.

Compression is activated in movedat by using the -z command line option.  For example:

movedat -z user@example.com:/path/downloadme /local/destination

Compression should only be used on files known to contain compressible data, such as text documents.  For these data types, compression may increase transfer speeds by three times or more, on top of MTP's throughput gains.

ExpeDat uses the same compression algorithm as Zip and Gzip.  Data which compresses well using those utilities will also compress well with ExpeDat.

Compression is very CPU intensive.  Data files which are already compressed, encoded, or encrypted, will not benefit from compression.  If the server or client is CPU limited, enabling compression may severely reduce performance.  If you are on a very fast network, even compressible data may move faster without compression due to the CPU overhead of compressing it.  See Tech Note 0014 for tips on deciding when to enable compression.

The best way to tell whether a given file type will benefit from compression when transferring to a particular server is to experiment with the setting both on and off to see which is faster.

Compression also uses extra memory, as network data must be buffered for the compression engine.  If your network is very fast and your latency is very high, then you may need to increase the size of the compression buffer.  The buffer should be at least twice the bandwidth-delay-product of your network path.  (Multiply the path bandwidth in bits-per second by the latency in milliseconds, then divide by 4096000.  The result is the number of kilobytes recommended.)  The default value of 16 is adequate up to a gigabit network with 75ms latency, or a 100 megabit network with 750ms latency.

The StreamSize option only affects buffers used by the movedat client.  If you find it necessary to increase this value, you should increase the server StreamSize as well.

Older servers and servers where compression is disabled will return an error if you attempt a compressed transaction.  Inline compression cannot be used with Streaming Folders or Object Handlers.

Since compression changes the amount and timing of data being sent, progress reports may be inaccurate while using compression.