on 09-16-2016 10:13 PM
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 |
Out of interest, what kernel mode are you using in Sybase 15.7 and Sybase 16 ?
What version of Sybase 16 are you using ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"<snip>
We see the WaitTime in ASE16 is 1/3rd of what it is in ASE157.
</snip>
That is music
Cheers
Avinash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.