Increasing your Full Text Indexing Processing Power
| Applies To | |||
| Product(s): | ProjectWise Full Text Indexing Server | ||
| Version(s): | 08.11.11.123+ | ||
| Environment: | Server2008+ with a dedicated Tail Server | ||
| Environment: | ProjectWiseIndexing Server Requirements | ||
| CPU: | Minimum of 4, recommend 8 | ||
| RAM: | Minimum of 12gb, recommend 16gb | ||
| Original Author: | Marty Nickel | ||
Overview:
This technote will describe how to add additional processors to increase Full Text Indexing for ProjectWise. Please take note of the minimum requirements above, this will not work properly and is not supported unless the minimum requirements are met.
Please make a backup of your Orchestration Framework database before following this technote. This will allow you to scale back to the original configuration in case this does not work out for you. If it does not work for you, just restore the original database over the newly configured database.
In order to get the processing to work as fast as possible, please follow this blog on how to properly configure the Full Text Indexing values in your ProjectWise Administrator:
The ftr-add-multiple-queues.sql file can be found here. There are instructions as well as notes inside of the file:
Setup:
- Stop Orchestration Framework on your head and tail server
- Run this query on your Orchestration Framework database to check how many processors you have and to make sure the server name is right: select * from orchShepherdProcesses
- Edit the @MachineName value in the attached ftr-add-multiple-queues.sql to represent your FTR server
- Run the attached ftr-add-multiple-queues.sql query after editing the lines
- Start your Orchestration Framework Administrator
- Manually map the new processors in the Orchestration Framework Administrator to represent the picture below.
- Start Orchestration Framework on your head and tail and it should process now
Notes:
After testing it appears that adding one extra set of processors to bring it up to two sets of processors is the best approach, three total sets were attempted but it tended to max the server's resources out and make it unresponsive. Please let TSG know if you have any questions on this technote.