Performance Considerations

The performance of synchronizing and searching data on the client depends on the size and complexity of the data model and the offline dataset.

If in addition large data volumes are involved, synchronizing can be very time consuming.

Each dataset is synchronized synchronously in one server request and must be transferred before a timeout occurs:

For a thin connection (e.g. GSM) the timeout hardly ever occurs. A timeout only occurs if time runs out before the first response package is transferred. A full synchronization on a thin connection will probably take a long time.

Do not use link fields ("Z fields") in your offline data set. Each offline dataset package is requested with one SQL statement, but the server might execute additional read operations for each record containing link fields.

When a dataset is requested, the following is applied and can result in complex SQL statements:

To limit the duration of synchronization, you can: