November 11, 2020 at 1:05 am
Attached file shows the top waits...
PARALLEL_REDO_WORKER_WAIT_WORK.: Not sure how relevant this may be for this morning Latency reported by multiple users accessing a number of web pages and apps that connect to this server.. just seeing it first time
But this wait type has been predominantly much higher than all other waits. Comparing to some past values could answer more..
This is something new to me as it is related to Always ON replicas, I am not knowledgeable on this wait type (yet).
Pinal Dave said though that this wait parallel redo can be disabled by trace flag 3459..
(not sure yet what consequences it may bring about as a trade off though…). CAN SOMEONE PLEASE SHED SOME LIGHT ON THIS WAIT TYPE and is it even worth paying attention at?
THANKS!
Likes to play Chess
November 12, 2020 at 1:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
November 17, 2020 at 3:50 pm
Looks like you are using Always On.
Read this wait info from sqlskills.
https://www.sqlskills.com/help/waits/parallel_redo_worker_wait_work/
"This wait type is one that I usually filter out as a benign wait when doing wait statistics analysis as it is documented as not being indicative of a performance issue.
You can read more about parallel redo in
"
when it comes to wait types, i usually go to sqlskills they have a vast library with all of them and a little description and in some cases even with examples.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply