Long Perform Maintenance Task Execution and request/ task thread settings

[enistri_devo (Emanuele Nistri)]

Hi @rabshrestha,

@rabshrestha

Task threads handle background tasks while request threads process user requests for access and other actions.

Generally yes.

@rabshrestha

Any time above task runs on Task Server A, the execution takes more than 10 mins while if it runs on Task Server B (which has TASKTHREAD value defined), the execution is super fast like in secs.

About that, It could depends from varius factor, some on IIQ some on server.
On IIQ side:
you can define the max numbers of thread(on Server object) that you want each server must use. Generally on IIQ you can set the max number for the task server and max number -1 for UI server, to not affect the user experience. Also you can set on Request Definition object the max threads for each actions and you can set the max number of thread for partitioning.
For example, if you 2 UI with 4 cpu for each one and 2 Task with 8 for each one, you can set 8 for on each server object for the task server and 3 for the UIs. On request definition and for partitioning you can use at least 22 threads.

So you can review if the configuration on your IIQ its correct and both server have the same conf.

On Server side:
understaning what happens on server its little more complicated. You must to analize the processes, the memory usage etc… On a server thare are a lot of thing can cause preoblems. I suggest to you to make a little analisys and performance test and check the KVM settings. Take a look on my post for it.