Minimize Update Latency for Replicated Tables

Keep in mind that when an application updates a replicated table, SQLFire performs the update on each member that hosts a replica of the table. The update latency for replicated tables increases with the number of SQLFire members that host the table.

SQLFire clients experience the update latency at different times. Peer clients incur the latency cost at execution time, while thin clients incur the latency cost only at commit time.

When possible, update highly-replicated tables outside of larger transactions.