Sometimes my e-mailxtender index very slow, very, very slow. I have to stop Journal to down private queue Index but, sometimes I have use "readmsmsq" and send items from this queue to txt file.
I have modify the key "Maxnumindexprocesses" in windows Registry to 6 but this is not the solution.
MaxNumIndexProcesses should not be more than 2x processor cernels (= 2 x number of processors you see in the task manager > Performance). Unfortunately for you, the amount of RAM doesn't help.
under Programs > Legato EmailXtender > Support > EmailXtender Performance there is an indicator for the processor utilisation.
This'll give you the insight of what the processor is busy with. -> I only get more than 50% utilisation if reindexing some volumes. Otherwise this service has only peaks around 30%.
Are the disks for the index fast enough; are they keeping up with the load?
Hope this helps. Don't mind getting EMC support involved. They are good in tuning a system.
wow, 8 processors (probably 4 physical?) is quite something. What physical hardware do you have? Well, you can try changing the MaxNumIndexProcesses to 16; though this sounds high. If you have had 6 before, you might want to start with 12.
This value will allow more processes, but the system will decide to create/use them. My MaxNumIndexProcesses is set to 8, but see only 3. Only when I had a corrupt index and need to reindex a lot, this will increase over time (some minutes). - exIndexSrvc is the service, but the exIndex, exIndex#1, etc. will do the work.
Sorry, don't understand what you mean by "what is the instance to processor use". There you'll see how much processor utilisation is required for each service/task.
Thoppay
20 Posts
657
0
Posted August 17th, 2007 11:00
Usually, the indexing process is more processor intensive.