I know that anyone in Java can be used to access any thread's CPU.
However, I believe that an actor can be determined to perform from the thread pool on any thread. Then the call from the same actor to the getCurrentThreadCpuTime can call the call completely unrelated.
What is the above truth? If so, is there any way to find the use of CPU usage by the actor himself?
Your thinking is correct.
Akka, by default, provides free threads from the pool of threads, there is no promise that threads from pool will be used for each message sent to an actor (though Batching will mean that the message sent to the same actor will appear towards the same thread). Akka thread permits the configuration of the pool, and it may include configuring a single formula for an actor, although sharing of threads in many artists avoids some weaknesses of SEDA architecture (where this multi-socket set Ups may experience increased latency).
The use of CPU in the best time in Java is difficult to use. There is not much on the way for Java delegates on the OS thread scheduling, and in the way of questioning that information from the OS. Use Acka's thread pool, and separate the actor from the scheduling of runtime and it helps us to say that there is no answer; There is no supported way of getting accurate CPU usage on a per-actor basis.
As an alternative, you can set the time of the wall clock within each actor. It will be easy by adding your cover to get the act of every actor. TypeSafe was a monitoring tool for Akka, which they had and instead started providing enterprise monitoring.
Comments
Post a Comment