I am a bit confused as to the optimum setting for the Search Index concurrency limits. Looks like the default is 2.
The index service uses a lot of CPU, so I want to reduce that.
I do notice that the update requests come and go. Is this an indication on how many concurrent connects I should allow?
Do I actually need the index service at all? What does it actually do? How do I turn it off for individual mailboxes/post offices?
Search Index properites
-
- Site Admin
- Posts: 9738
- Joined: Mon Mar 22, 2004 4:44 am
- Location: Melbourne, Victoria, Australia
Re: Search Index properites
Hi,
If the service is consuming high CPU then yes you can lower the concurrent thread count to 1 to see if this helps. The indexing service is used to index mailbox data for the web mail search page. There is no way to disable it at the mailbox or postoffice level. This can only be disabled globally. You can setup a Windows scheduled task so that the service executes during low traffic times. Please consult with Windows docs on how to create scheduled tasks.
If the service is consuming high CPU then yes you can lower the concurrent thread count to 1 to see if this helps. The indexing service is used to index mailbox data for the web mail search page. There is no way to disable it at the mailbox or postoffice level. This can only be disabled globally. You can setup a Windows scheduled task so that the service executes during low traffic times. Please consult with Windows docs on how to create scheduled tasks.
Regards,
Ian Margarone
MailEnable Support
Ian Margarone
MailEnable Support