Written by

Question water huang · Sep 1, 2024

how to kill %SYSTEM.WorkMgr process

i use %SYSTEM.WorkMgr  to handle data by multicompile=1,but i find that,after WaitForComplete,the processes created by %SYSTEM.WorkMgr  are still stand by,

and status is evtw,after i run many times,the processes are more.and this will cause server falls into trouble.so my question is ,how to kill the processes that created by using the %SYSTEM.WorkMgr,and how to avoid  to make the server falls into trouble,why  this will cause server falls into trouble。and is there a better way to handle data by mult process?

Product version: Ensemble 2016.1
$ZV: Cache for Windows (x86-64) 2016.2.3 (Build 907_11_20446U) Thu Nov 12 2020 16:56:45 EST

Comments

water huang  Sep 3, 2024 to Jhuffare Khan

thanks,but  it`s not i want,code does not know the pid

0
Mark Hanson  Sep 3, 2024 to Chris Stewart

This is correct. Once we start a worker job we keep it around for the next time we need a worker job to avoid the overhead of starting a new process. The workers should not be using any significant memory or CPU and will time out automatically after a while so you can leave them alone.

0