Orleans extreme slow when debuging

[montella1507]

Hi,

anyone experiencing issues with debugging on MacOS M2 / Rider?

Orleans is like 500x times slower when debugger is attached.

Orleans 7.0, .NET Core 7.0

[montella1507]

When i Detach debugger it runs normally afterward...

[ReubenBond]

Is that 500x number measured or an estimate? Are you attaching a debugger to a Debug build of your application, or a Release build? I would expect it to be about 10x slower, but it depends on what you're doing. I'm also not familiar with the debugger on macOS. Maybe it's much slower.

[cmeyertons]

It may be related to dotnet/runtime#38736 - I've seen this problem crop up in highly parallel, multi threading code, which Orleans naturally leans into.

[montella1507]

Seems so! Thank you

Unfortunately i can confirm this:

This is extremely frustrating, and makes debugging barely functional.
It's quicker to debug using log statements.

So i hope it will get fixed soon

[slonopotamus]

We're also seeing this with .NET 6.0 + Orleans 3.6.2 and believe that dotnet/runtime#38736 is the root cause. And no, 500x is not an exaggeration.

[ReubenBond]

It sounds like this is a Mac-specific issue. Please👍 that issue and/or respond to it to try to get it resolved. It looks like it has quite a few 'votes' already...

[montella1507]

I Will try the performance on Windows then.

[montella1507]

@ReubenBond

Windows - JetBrains Rider- 10700k, 64GB RAM, 200 grains:

• no debug 280 - 330ms
• debug 1300 ms

macOS - JetBrains Rider- M2 Air , 24GB unified, 200 grains:

• no debug - 300-370ms
• debug - 22 000 - 37 000 ms

So it may be mac-specific issue

[mkuennek]

We also encountered this issue while evaluating Orleans, but for both Windows and MacOS. Really rough to use Orleans like this.

[ReubenBond]

@mkuennek is performance under the debugger equally bad on Win & Mac? When you run under the debugger, are you also changing any other settings, such as log levels? Please add feedback (thumbs up, comment with info) to the original .NET runtime issue: dotnet/runtime#38736

EDIT: also, which debugger are you using on Windows, @mkuennek, is it VS or Rider?

[mkuennek]

@ReubenBond Without having any hard number I would say both Mac and Windows experience the same performance degradation. Both platforms start showing same types of warnings and errors(slow storage access, failing to activate grains). We do not change any other settings. Both runs were in Debug configuration with same log levels, etc.

Thank you for the feedback. Already voted in the mentioned runtime issue.

Both platform tests were done using the current version of Rider but we also had another developer using Windows with VS report this problem.

[ReubenBond]

Thanks for the info, @mkuennek. Hopefully we can get this fixed in the .NET Runtime and/or debuggers. I'm not sure why this is more of an issue on mac than Windows. My inkling was that the issue was related to the way that Rider's debugger handles the notification, but if behavior is the same on Windows under VS (which I have not yet experienced), then perhaps that is not the case. I've asked for more information on the dotnet/runtime thread.

[mkuennek]

I just installed VS to check it myself. The behavior is the same as with Rider.

If you think a small project for reproducing this issue could help, I can try providing one.

[ReubenBond]

Thanks. The dotnet/runtime thread has a minimal repro already. The problem seems to be well understood by the runtime engineers and we're just waiting for a fix now.