troubleshooting_-_synchronizing_local_dataset_slows_down_system_five_for_all_users
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | troubleshooting_-_synchronizing_local_dataset_slows_down_system_five_for_all_users [2008/07/15 10:32 (16 years ago)] (current) – created james | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== Troubleshooting - Synchronizing Local Dataset Slows Down System Five for All Users ===== | ||
+ | |||
+ | ==== Problem ==== | ||
+ | |||
+ | When synchronizing a Standalone LAN dataset with changes from the main dataset, other users working in the main dataset experience extreme slowness. If the synchronization process runs to completion or is stopped, performance returns to the normal level. | ||
+ | |||
+ | |||
+ | ==== Solution ==== | ||
+ | |||
+ | The Standalone LAN application (Standalone Monitor) may be pushing the Pervasive database engine beyond its configured limits. The root of the problem is that the Pervasive engine by default is configured with fairly conservative default settings. Adjusting these settings should prevent performance from degrading during a synchronization operation. | ||
+ | |||
+ | The two settings that are worth checking are Communications Threads and Number of Input/ | ||
+ | |||
+ | {{faq: | ||
+ | |||
+ | By default, the Communications Threads setting is set to 16. Pervasive advises that this should be tuned up to a value of 32, one for each connected workstation on your network. For larger installations where more than 32 workstations are connected at the same time, they advise using the Pervasive Monitor to help determine a value for this setting. | ||
+ | |||
+ | By default, the Number of Input/ | ||
+ | |||
+ | In order for these changes to take effect, the Pervasive server must be restarted. | ||
+ | |||
+ | < |
troubleshooting_-_synchronizing_local_dataset_slows_down_system_five_for_all_users.txt · Last modified: 2008/07/15 10:32 (16 years ago) by james