Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

find out why ASystem runs like crap with multithreading on my phone (except when there is a debugger) #18

Open
Doraku opened this issue Aug 11, 2018 · 5 comments

Comments

@Doraku
Copy link
Owner

Doraku commented Aug 11, 2018

Seem to be related to DVFS

@Doraku
Copy link
Owner Author

Doraku commented Feb 4, 2019

playing around with SpinCount of the WorkerBarrier ManualResetEventSlim did not change anything.

@dzmitry-lahoda
Copy link

have you found root cause? I may look into in some time at future.

@dzmitry-lahoda
Copy link

what are steps for repro?

@dzmitry-lahoda
Copy link

guess, there is to much parallelism(up to for loop like spins)? may some primitives on mono are badly written?

@Doraku
Copy link
Owner Author

Doraku commented Aug 10, 2019

I only observe this problem when running on my phone or my surface go when they are unplugged. I should be able to create a small project showing this when I get back in a couple of day if you are interested. The tasks take forever to execute while there is almost nothing to process, as if the mobile cpu were severly underclocked (but ut run fine in mono thread). Using thread or thread pool didn't change anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants