-
Notifications
You must be signed in to change notification settings - Fork 101
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
Multiple SQL Nexus fixes (#250, #251, #238, #254) #259
Conversation
… window when Relog is importing data
…ariousFixes_PijoCoder
…ariousFixes_PijoCoder
…ich were saved because the "Save My Options" is being enabled
…through it. Also modified a few option names ot distinguish them
…ariousFixes_PijoCoder
…ariousFixes_PijoCoder
REDO_THREAD_PENDING_WORK wait type is now ignorable type, which means it will not show up in the Bottleneck Analysis report as a bar in the bar chart. Currently I have one nexus loaded where a related wait is the highest one Current nexus version Version from the PR. We no longer see the REDO_THREAD_PENDING_WORK, but we still can see PARALLEL_REDO_WORKER_WAIT_WORK. I'm wondering if this one could also be ignored |
Yes, there are many such wait types. Can you file an issue on Github and add this and this other one I sent to Haci the other day
QDS_ASYNC_QUEUE be an ignorable wait type?
If you can think of others add them to the list.
Thanks
…________________________________
From: Andre Savioli ***@***.***>
Sent: Monday, November 13, 2023 5:38:45 AM
To: microsoft/SqlNexus ***@***.***>
Cc: Joseph Pilov ***@***.***>; Author ***@***.***>
Subject: Re: [microsoft/SqlNexus] Multiple SQL Nexus fixes (#250, #251, #238, #254) (PR #259)
REDO_THREAD_PENDING_WORK wait type is now ignorable type, which means it will not show up in the Bottleneck Analysis report as a bar in the bar chart.
Currently I have one nexus loaded where a related wait is the highest one
Current nexus version
[image]<https://user-images.githubusercontent.com/49494532/282449422-b3034f73-19a9-43c1-86fa-b4674e27dac0.png>
Version from the PR. We no longer see the REDO_THREAD_PENDING_WORK, but we still can see PARALLEL_REDO_WORKER_WAIT_WORK. I'm wondering if this one could also be ignored
[image]<https://user-images.githubusercontent.com/49494532/282449366-d5312f8e-6400-449e-ac8d-5e116daf3f74.png>
—
Reply to this email directly, view it on GitHub<#259 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFTOCHKJ5BZWUJKFUV2ICSTYEIBD7AVCNFSM6AAAAAA56EHTXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXHE4TGNRWGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Performed the tests below
Initially I tested enabling the option minimize cmd during the relog. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can. Paul Randal agrees |
2931640
Allow the ability to minimize Cmd prompt window when Relog.exe imports Performance .BLG files into SQL Nexus
Allow the ability to import XEL files using local server time, rather than UTC time (default) via ReadTrace
Fixed "Save my options" functionality in the import window to ensure the import options were really saved. Some of the options weren't saved before even though the GUI shows the boxes are checked.
To test this last fix,
REDO_THREAD_PENDING_WORK wait type is now ignorable type, which means it will not show up in the Bottleneck Analysis report as a bar in the bar chart.