Skip to Content
0
Former Member
Sep 16, 2016 at 09:13 PM

Waitevent 250 in ASE157 and ASE16

229 Views

Say for example if you are executing a huge sql file with each statement separated by a "go".

select 1

go

select 1

go

.......go this way up to 50000

go

select * from master..monProcessWaits

where SPID = @@spid

go

The amount of Waits for WaitEventID will be equal to the number of "go" statements in the file. We have measured the Waits and WaitTime between ASE16 and ASE157. We see the WaitTime in ASE16 is 1/3rd of what it is in ASE157.

Why is this so important?

If you are running some benchmarking tests between ASE157 and ASE16 then this becomes an important factor. It will never be like for like.

However, we think this is a good improvement in ASE16 and will help improve elapse times.

Version ElapsedTime_ms Waits WaitTime_ms ASE16 113,416 2,906,998 983,803 ASE157 276,943 2,907,216 2,581,027