FAQ Home > Common Errors and Issues

inContext is slowing my down my server, how can I prevent this from occurring?
Article ID: #000141

inContext, our spidering and content matching system, will launch a number of spiders at a time. While most servers can handle the default setting, some web servers may exhibit impact on performance.

As the system administrator, you can adjust how many spiders can run at any given moment, limit how many URLs a spider can work with at a time, and how many total URLs can be worked with by all spiders in a given launch.

For example, the default setting allows 400 URLs to be processed in a batch. In that batch, no more than 4 spiders can index at a time. Each spider is limited to 40 URLs at a time.

These values, 400, 40, and 4, can be changed by adding the following lines to your /globals/globals_custom.php file:

$action_vars["incontext_thread_count"] = 4; //Max number of threads per batch to create
$action_vars["incontext_urls_per_thread"] = 40; //Max URLs to process per thread
$action_vars["incontext_max_urls_per_batch"] = 400; //Max URLs to process per batch

To "tone down" the inContext process, we suggest lowering the number of incontext_tread_count's in increments of 1. Additionally, you can lower the incontext_urls_per_thread value in increments of 5. In each case, you should observe system performance after changes have been made for at least one hour to determine if the changes provided the necessary improvements.

Additional Performance Tip:
If INNODB is available for your MySQL server, change the table inclick_incontext_terms to an INNODB.

[ Search FAQ | FAQ Home ]