User Tools

Site Tools


troubleshooting_-_synchronizing_local_dataset_slows_down_system_five_for_all_users

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

troubleshooting_-_synchronizing_local_dataset_slows_down_system_five_for_all_users [2008/07/15 10:32] (current)
james created
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/​Output Threads. These can be found in the Pervasive Control Center on the server under Configuration -> Server -> Performance Tuning. The screenshot below shows the location of these settings in the Pervasive Control Center for version 8. Different versions of the Pervasive Control Center may look differently.
 +
 +{{faq:​faq:​perftuning.jpg|}}
 +
 +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/​Output Threads setting is set to 4. Pervasive'​s recommendation is to size this value based on the number of files that the engine usually has open. You can use the Pervasive Monitor to get an idea of the number of files that are open by the engine at any given time. Note that the Pervasive Monitor is an advanced tool, you should consult Pervasive documentation to get information on how to use it correctly. Without using the Pervasive Monitor, a good starting value for the number of I/O threads is between 24 and 32.  ​
 +
 +In order for these changes to take effect, the Pervasive server must be restarted.
 +
 +<​note>​It'​s important to note that increasing the values for these settings can hurt performance overall. Generally speaking, you should only have to change these settings if you are encountering performance problems, and changes you make should be conservative.</​note>​
troubleshooting_-_synchronizing_local_dataset_slows_down_system_five_for_all_users.txt ยท Last modified: 2008/07/15 10:32 by james