Pausing the sifter during periods of heavy database usage

Pausing the sifter during periods of heavy database usage

You can pause the sifter during times of heavy database access. This frees up database resources for other activities during heavy database activity. The time value for this key is formatted exactly like the UNIX crontab. To configure the sifter to 'sleep' at 11 a.m., for example:
Stop the LikeMinds server inside the WebSphere Application Server.
Use any database modification tool to connect to the database, and to enter the following SQL statement:
INSERT INTO lps_cfg (name, value) VALUES ('ratingMentor.pause_sifting_at','00 11 * * *')

Start the LikeMinds server inside the WebSphere Application Server.

If you set mentor_set_name.pause_sifting_at, configure the time at which you want the sifter to wake up afterwards. To configure the sifter to 'wake up' at 4 p.m., for example:

Stop the LikeMinds server inside the WebSphere Application Server.

Use any database modification tool to enter the following SQL statement:

INSERT INTO lps_cfg (name, value) VALUES ('ratingMentor.resume_sifting_at','00 16 * * *')

Start the LikeMinds server inside the WebSphere Application Server.