This content has been translated automatically.  Click here  to view the French version.
Help / WLanguage / Managing databases / HFSQL / Managing HFSQL Client/Server
  • Overview
  • How to?
  • Principle
  • When should the network frames be compressed?
  • How to use the compression of frames?
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures
Compressing frames (DSL, 3G, Edge, VPN, ...)
HFSQL Client/ServerAvailable only with this kind of connection
A frame is a packet ot data that flows through the network.
HFSQL Client/Server, like all the DBMSs, is using the frames to establish the communication between the Server and the Client computer.
The response speed of a server depends on the circulation speed of the frames through the network and on the size of these frames.
In local network, the speed is so high that the size of the frame is not very important.
For a remote access (ADSL, 3G, VPN, ...), the size of the frame is more important. In this context, a reduction of the size of the frames increases performance. In a context of remote communication, the compression of the frames is very important especially if the connection speed is slow and if the invoicing depends on the volume of transmitted data.
How to?


The principle for compressing the frames is as follows:
  1. The data to transmit is compressed on the server (or on the client).
  2. The compressed data is transmitted to the client (or to the server).
  3. The data is decompressed on the client (or on the server).
The benefit brought by the data compression depends on the configuration used. For example, if the client computer is a powerful computer that uses a slow connection, it may be interesting to compress the frames: the time spent for the compression/decompression will be insignificant compared to the time saved when transmitting data.

When should the network frames be compressed?

The choice must be based on 3 parameters:
  • the speed of the network used,
  • the CPU performance of the client computers
  • the type of the transmitted data.
The importance of each parameter depends on the two other ones so no standard formula is available. However, you will find some tips that help you make this choice:
If the speed of the network used is greater than 10 Mbits/second, there is no need to compress the frames.
If the network used (GRPS, EDGE or 3G type) is invoiced according to the amount of transmitted data, we advise you to compress the frames in order to reduce the cost.
If an important amount of data (binary memo) is transmitted (images, video, zip sound, etc.), the compression of frames will be useless.
In all the other cases:
  • on client computers equipped with high-performance processors and if text or text memo data is used by your application, it may be interesting to compress the frames.
  • on client computers equipped with low-performance processors, it may be very interesting to compress the frames if the transfer rate is quite slow.
It may be interesting to perform comparative measurements by using the performance analyzer.
HConnectionQuality can be used as a last resort to compare the performance of compressed and decompressed connections.

How to use the compression of frames?

The compression of frames is a property of the connection.
To use the compression of frames:
  • if the connection is defined in the data model editor, you have the ability to modify the characteristics of the connection:
    • on the "Analysis" tab, in the "Connection" group, click "Connections".
    • Select the desired connection.
    • display the "Advanced" tab and check "Compress the data".
  • if the connection is defined through programming, several methods are available:
Minimum version required
  • Version 14
This page is also available for…
Click [Add] to post a comment

Last update: 07/06/2023

Send a report | Local help