Indexing Service

Post your MailEnable suggestions here.
Post Reply
dedicate-it.net
Posts: 6
Joined: Mon Feb 22, 2021 8:30 pm

Indexing Service

Post by dedicate-it.net » Tue Jul 27, 2021 12:01 am

-- request that this service be set to use "Below Normal" thread priority.

We have been dealing with loading and "stall" issues on our ME installation - mainly due to some users having large inboxes (which is a war we cannot seem to win as a reseller).

In our testing, we have found if we set the MEMIS.exe Indexing service to "below normal" priority, that the server is much more stable, and does not have performance issues for IMAP users, as well as delays and stalls on our Plesk management software. Plesk offers "monitoring" that runs in the background - and we have found that many background processes on this server get hung waiting for processor due to 100% CPU usage of MEMIS.exe --

When adjusting the process priority manually, we see returned performance even when MEMIS attempts to use high processor for large indices.

Understandable if this is not an option - but wanted to offer as a suggestion.

ME is extremely efficient on resources with exception of processor hogging by MEMIS (which fights other ME processes for CPU cycles).

Thank you for your time.

poweredge
Posts: 127
Joined: Sat May 29, 2021 11:16 am

Re: Indexing Service

Post by poweredge » Fri Jul 30, 2021 3:56 am

Could it be this bug?
https://mailenable.com/forum/viewtopic.php?f=14&t=43976

dedicate-it.net
Posts: 6
Joined: Mon Feb 22, 2021 8:30 pm

Re: Indexing Service

Post by dedicate-it.net » Fri Oct 29, 2021 1:51 pm

No - in that case, there was a full application fault in MEMIS.exe refeferencing a missing object (which seems to be resolved in newer versions).

This is more along the lines of CPU resources consumed by MEMIS during indexing.

Currently, we watch the MEMIS process and set it's priority to "Below Normal" whenever it or the server is restarted - this greatly curbs the non-responsiveness from the server when MEMIS is processing large indices.

Whenever MEMIS is allowed to run at normal priority, it doesn't play nice with other applications at the same priority level - often consuming 100% processor while indexing, and limiting threads from other applications from executing. When we set the the "Below Normal" priority, this "hogging" of CPU plays much nicer with other applications and CPU usage (including not "stalling" our monitoring software).

Post Reply