Comments
Sort by recent activity
Yes, although I wouldn't guarantee this as a universal answer. In our case in was due to a virtual NIC misconfiguration in one of our VMs, which was running on VMWare VSphere. To fix the problem we needed to disable receive side coalescing on the guest NIC. To do this you can run the following from an elevated Powershell prompt: Disable-NetAdapterRsc * As I say, this fixed the issue for all, and all our troublesome queries started running in around 1ms, but I wouldn't guarantee it will work for everyone. HTH. Bart / comments
Yes, although I wouldn't guarantee this as a universal answer.In our case in was due to a virtual NIC misconfiguration in one of our VMs, which was running on VMWare VSphere.To fix the problem we n...
Thanks Alex,
There is also a workaround, in that you can just open a query with EXEC [ClassName].[TestSprocName]
and set a breakpoint on that but it would be great to have something a bit more seamless.
Cheers, / comments
Thanks Alex,
There is also a workaround, in that you can just open a query withEXEC [ClassName].[TestSprocName]
and set a breakpoint on that but it would be great to have something a bit more sea...
Hey, don't worry about the word wrap - just found it on the output pane's context menu. Be worth adding an option to the toolbar as well though. / comments
Hey, don't worry about the word wrap - just found it on the output pane's context menu. Be worth adding an option to the toolbar as well though.
No stress - thanks Eddie. / comments
No stress - thanks Eddie.
Cheers Eddie - appreciate it. / comments
Cheers Eddie - appreciate it.
Thanks Jessica! / comments
Thanks Jessica!
Hi Eddie,
Thanks very much - appreciate it.
Couple of other things:
- It would be great if double-clicking a node opened up the source code,
- Similarly to the context menu Select > Connected Objects option, a Show > Connected Objects would be really helpful (or, better yet Show > Objects This Depends On, and Show > Objects That Depend On This).
(I know, give 'em an inch...)
Thanks! / comments
Hi Eddie,
Thanks very much - appreciate it.
Couple of other things:
- It would be great if double-clicking a node opened up the source code,
- Similarly to the context menu Select > Connected Objec...
Thanks Jessica,
I've seen it happen on Windows Server 2008 R2, Windows Server 2012, Windows 8, and Windows 8.1, both over RDP and locally. I demonstrated the problem, which is extant in the latest release, for Ben the other lunchtime.
What seems to be happening is that the bars in the timing columns, and the lines in the navbar on the right, are being normalised against the overall timings for the period selected in the timeline, NOT against the longest running line in the file. This is a problem because if, for example, you're looking at wall clock time, the real performance problems are generally not in the supposedly most expensive stack trace (which is often something like "waiting for synchronization").
As I say the issue is that you have to find the most expensive lines of code by inspection, which is obviously error prone, not to mention time-consuming for larger source files.
Hope that's helpful.
Thanks, / comments
Thanks Jessica,
I've seen it happen on Windows Server 2008 R2, Windows Server 2012, Windows 8, and Windows 8.1, both over RDP and locally. I demonstrated the problem, which is extant in the latest ...
Thanks Jessica. The machine's running Windows Server 2008 R2 SP1, in case that's any help? / comments
Thanks Jessica. The machine's running Windows Server 2008 R2 SP1, in case that's any help?
It's OK, it hasn't changed. The shortcut for Reflector's search, which you can find on the Tools menu, is F3. CTRL+F has always brought up the text search when the decompilation pane has input focus. / comments
It's OK, it hasn't changed. The shortcut for Reflector's search, which you can find on the Tools menu, is F3. CTRL+F has always brought up the text search when the decompilation pane has input focus.