May 24, 2018 at 1:27 pm
HI All
I have 2 environments running on the same version of SQL, exact same tables ..... but when i run the same update script on both instances one is fast and the other is slow.
when i compare the execution plan they are both the same on each server :ermm: any ideas where to look from here?
on the poor server the process has a wait type SOS_SCHEDULER_YELD
thanks in advance
***The first step is always the hardest *******
May 24, 2018 at 1:31 pm
SGT_squeequal - Thursday, May 24, 2018 1:27 PMHI AllI have 2 environments running on the same version of SQL, exact same tables ..... but when i run the same update script on both instances one is fast and the other is slow.
when i compare the execution plan they are both the same on each server :ermm: any ideas where to look from here?
on the poor server the process has a wait type SOS_SCHEDULER_YELD
thanks in advance
What other processes are running on the slower server? Is the underlying hardware the same? Is it hosted on a VM which is stressed?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
May 24, 2018 at 1:36 pm
SGT_squeequal - Thursday, May 24, 2018 1:27 PMHI AllI have 2 environments running on the same version of SQL, exact same tables ..... but when i run the same update script on both instances one is fast and the other is slow.
when i compare the execution plan they are both the same on each server :ermm: any ideas where to look from here?
on the poor server the process has a wait type SOS_SCHEDULER_YELD
thanks in advance
Are the environments the same? I may be wrong but it looks like you are having CPU issues in the environment getting SOS_SCHEDULE_YIELD waits.
If you have time check out this webinar: http://info.sentryone.com/e1t/c/*W4G8NLm6GFvYxVqckT-5q70Nd0/*W2pn4j65-Cg46W8tmDHY76KWb00/5/f18dQhb0S4013vgP8MVWVCC-3wxhwBN1tRbdYkT-ZZW96YdMH13fTrmN6lMqkpRJKHmW1xb9B97lGHWqW4lqrgp6S5Jd0N50zd8lkxB0HW2zDFp18c6PdcW4qs8sf4pyRvPW9gXGnH8pMjF2W5L1KJy4yFg_4W15Y4xR3JYWN6W6x4pWz6_BvwYW2G_cGd57NHTKW7hJWFB5GBptWW6tnmsr5dvdpgW1k5Bbr4gxlS2W6wls726mMDzkW5rxYfc22T9LPN7wwQnb3fgTwW8VM6ry7XdjTCW6Lqm3l53D_nDW3g0SM98l_394N6b86-dJkN9DVBwxlG8B2VghVJSy9C61_LX2VRJgWs7271QRW69hJh27k7HfvN1NjM8XL6q28W7fm98S7X9bmmW8ZCZlX2tTxnWM1y36dqV4lfW16jQQs3bl4VKN2RsHPG9Nh80W7dd51z7gWZT_W119qX25kTKmGW3DPHJz2fyv0yW72Vc8f7YhMDqW8L0sd41V9h79W6Xp3qR4kh6TgW14rqLN2fycbzW8kb7lL3VZSFzW3YQ6z-8wH6RHW5nVZ5R18c17sN61Yvc_ZhqJSW6Cl_NJ7TCN93V8CRGK2cb8GRW5DYc403nsL9wW896WC56T5dbsW7N1fHK2S35wqW3BDhN_2TKks_W8dk1yN23rWXmW6QVfph8Vdw1DW8sFH1895cSMrW3pgkj97ZZV3yW43nvsv93g1hkW6ZL2cr20QFy0W5tZ6ML35zKl9111
May 24, 2018 at 1:41 pm
Hi Phil
its hosted on a VM and there are various processes running on poor performing server however, the majority are sleeping only a handful are background tasks
***The first step is always the hardest *******
May 24, 2018 at 1:42 pm
Lynn Pettis - Thursday, May 24, 2018 1:36 PMSGT_squeequal - Thursday, May 24, 2018 1:27 PMHI AllI have 2 environments running on the same version of SQL, exact same tables ..... but when i run the same update script on both instances one is fast and the other is slow.
when i compare the execution plan they are both the same on each server :ermm: any ideas where to look from here?
on the poor server the process has a wait type SOS_SCHEDULER_YELD
thanks in advance
Are the environments the same? I may be wrong but it looks like you are having CPU issues in the environment getting SOS_SCHEDULE_YIELD waits.
Hi Lynn
i had thought that it could be CPU however if i sum time from sys.dm_os_wait_stats this tells me for said wait time i have about 2% cpu pressure
***The first step is always the hardest *******
May 24, 2018 at 1:42 pm
Lynn Pettis - Thursday, May 24, 2018 1:36 PMAre the environments the same? I may be wrong but it looks like you are having CPU issues in the environment getting SOS_SCHEDULE_YIELD waits.
If you have time check out this webinar: http://info.sentryone.com/e1t/c/*W4G8NLm6GFvYxVqckT-5q70Nd0/*W2pn4j65-Cg46W8tmDHY76KWb00/5/f18dQhb0S4013vgP8MVWVCC-3wxhwBN1tRbdYkT-ZZW96YdMH13fTrmN6lMqkpRJKHmW1xb9B97lGHWqW4lqrgp6S5Jd0N50zd8lkxB0HW2zDFp18c6PdcW4qs8sf4pyRvPW9gXGnH8pMjF2W5L1KJy4yFg_4W15Y4xR3JYWN6W6x4pWz6_BvwYW2G_cGd57NHTKW7hJWFB5GBptWW6tnmsr5dvdpgW1k5Bbr4gxlS2W6wls726mMDzkW5rxYfc22T9LPN7wwQnb3fgTwW8VM6ry7XdjTCW6Lqm3l53D_nDW3g0SM98l_394N6b86-dJkN9DVBwxlG8B2VghVJSy9C61_LX2VRJgWs7271QRW69hJh27k7HfvN1NjM8XL6q28W7fm98S7X9bmmW8ZCZlX2tTxnWM1y36dqV4lfW16jQQs3bl4VKN2RsHPG9Nh80W7dd51z7gWZT_W119qX25kTKmGW3DPHJz2fyv0yW72Vc8f7YhMDqW8L0sd41V9h79W6Xp3qR4kh6TgW14rqLN2fycbzW8kb7lL3VZSFzW3YQ6z-8wH6RHW5nVZ5R18c17sN61Yvc_ZhqJSW6Cl_NJ7TCN93V8CRGK2cb8GRW5DYc403nsL9wW896WC56T5dbsW7N1fHK2S35wqW3BDhN_2TKks_W8dk1yN23rWXmW6QVfph8Vdw1DW8sFH1895cSMrW3pgkj97ZZV3yW43nvsv93g1hkW6ZL2cr20QFy0W5tZ6ML35zKl9111
Blimey, that URL is well encrypted!
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
May 24, 2018 at 1:43 pm
Phil Parkin - Thursday, May 24, 2018 1:42 PMLynn Pettis - Thursday, May 24, 2018 1:36 PMAre the environments the same? I may be wrong but it looks like you are having CPU issues in the environment getting SOS_SCHEDULE_YIELD waits.
If you have time check out this webinar: http://info.sentryone.com/e1t/c/*W4G8NLm6GFvYxVqckT-5q70Nd0/*W2pn4j65-Cg46W8tmDHY76KWb00/5/f18dQhb0S4013vgP8MVWVCC-3wxhwBN1tRbdYkT-ZZW96YdMH13fTrmN6lMqkpRJKHmW1xb9B97lGHWqW4lqrgp6S5Jd0N50zd8lkxB0HW2zDFp18c6PdcW4qs8sf4pyRvPW9gXGnH8pMjF2W5L1KJy4yFg_4W15Y4xR3JYWN6W6x4pWz6_BvwYW2G_cGd57NHTKW7hJWFB5GBptWW6tnmsr5dvdpgW1k5Bbr4gxlS2W6wls726mMDzkW5rxYfc22T9LPN7wwQnb3fgTwW8VM6ry7XdjTCW6Lqm3l53D_nDW3g0SM98l_394N6b86-dJkN9DVBwxlG8B2VghVJSy9C61_LX2VRJgWs7271QRW69hJh27k7HfvN1NjM8XL6q28W7fm98S7X9bmmW8ZCZlX2tTxnWM1y36dqV4lfW16jQQs3bl4VKN2RsHPG9Nh80W7dd51z7gWZT_W119qX25kTKmGW3DPHJz2fyv0yW72Vc8f7YhMDqW8L0sd41V9h79W6Xp3qR4kh6TgW14rqLN2fycbzW8kb7lL3VZSFzW3YQ6z-8wH6RHW5nVZ5R18c17sN61Yvc_ZhqJSW6Cl_NJ7TCN93V8CRGK2cb8GRW5DYc403nsL9wW896WC56T5dbsW7N1fHK2S35wqW3BDhN_2TKks_W8dk1yN23rWXmW6QVfph8Vdw1DW8sFH1895cSMrW3pgkj97ZZV3yW43nvsv93g1hkW6ZL2cr20QFy0W5tZ6ML35zKl9111Blimey, that URL is well encrypted!
THe webinar is a SentryOne/SQLSkills partnership.
May 24, 2018 at 3:00 pm
SGT_squeequal - Thursday, May 24, 2018 1:42 PMLynn Pettis - Thursday, May 24, 2018 1:36 PMSGT_squeequal - Thursday, May 24, 2018 1:27 PMHI AllI have 2 environments running on the same version of SQL, exact same tables ..... but when i run the same update script on both instances one is fast and the other is slow.
when i compare the execution plan they are both the same on each server :ermm: any ideas where to look from here?
on the poor server the process has a wait type SOS_SCHEDULER_YELD
thanks in advance
Are the environments the same? I may be wrong but it looks like you are having CPU issues in the environment getting SOS_SCHEDULE_YIELD waits.
Hi Lynn
i had thought that it could be CPU however if i sum time from sys.dm_os_wait_stats this tells me for said wait time i have about 2% cpu pressure
You may want to check your schedulers to see if runnable tasks, queues are 0 (or near 0), active workers less than current workers, etc. Check several times or more:
SELECT
scheduler_id,
current_tasks_count,
runnable_tasks_count,
load_factor,
current_workers_count,
active_workers_count,
work_queue_count
FROM sys.dm_os_schedulers
WHERE scheduler_id < 700
Sue
May 25, 2018 at 5:23 am
Hi Lynn
Runnable task count is 0 and active workers are less that current workers.
What does come up with High CPU is a select statement getting info from sysprocesses but CPU looks ok
***The first step is always the hardest *******
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply