03 Nov 2022 03:32 AM - last edited on 03 Nov 2022 06:17 AM by Ana_Kuzmenchuk
I would like to ask about the meaning of the Background thread, what kind of transaction will be the Background thread? Is it a timed batch job?
Because when I observed "Detailed CPU consumption", I found that the "background thread CPU" was higher in a certain period than at other times.
Check out "Method hotspots" and saw "Request A" here (Background thread), but my client said that Request A should be in another service and not in the Background thread.
So how should I explain it to the client?
PS: I have a reference to this document, but I still don't quite understand it
Solved! Go to Solution.
Background thread CPU refers to everything that is happening not on a monitored request (purepath).
If we have a purepath for it, it will be Service request CPU.
If it makes sense for the customer, he can create a custom service for a method he is interested in and then we would capture purepaths for that method and the CPU value would move from background cpu to service cpu of that service.