Charm++ parallel programming system

[Ronak Buch <rabuch2 AT illinois.edu>]

dummy_thread_ep is essentially a placeholder for situations when the full provenance of the unit to be traced is unknown.  Do you have a suspicion of what code is actually running during those times?  We have a few potential ideas that may make such logs more informative, but to help you directly, it would be helpful to understand what exactly your program is doing at that point.

Is it using threaded entry methods or some other form of suspend/resume, for example?

On Thu, Nov 3, 2016 at 2:41 PM, Alexander Frolov <alexndr.frolov AT gmail.com> wrote:

Hi all!

I have got bizarre behavior of my Charm++ application. Profiling it with projections shows that   dummy_thread_chare::dummy_thread_ep is frequently called and consumes much of the run time. Can anybody tell me what does this function  for and when it is called by the rts? 

I've attached the screenshot of Timelines to the email.

Thank you!

Best, 

    Alex