PSLA-5
Open
Storage lock data in 2019.1 and later logs skewing results.
The storageup, and I suppose the storageupmaster possibly, are putting lock times on
other tables.
$ log2sql --version
log2sql, version v0.8.1 (branch: master, revision: c834aaf)
build user: rcowham@perforce.com
build date: 2020-09-05T19:01:35+0100
go version: go1.13.4
....
--- db.workingx
--- total lock wait+held read/write 0ms+31ms/0ms+1856ms
--- max lock wait+held read/write 0ms+31ms/0ms+1855ms
--- db.change
--- total lock wait+held read/write 7ms+1ms/2337ms+0ms
--- max lock wait+held read/write 7ms+1ms/2337ms+0ms
--- storageup/storageup(R)
--- total lock wait+held read/write 0ms+1635446ms/0ms+0ms
startTime endTime running user cmd pid tableName maxReadHeld maxWriteHeld totalReadWait totalReadHeld totalWriteWait
0 2020/10/13 16:55:29 2020/10/13 17:22:45 184 supadhyayula user-shelve 44149 change 1 0 0 1635446 0
The storageup, and I suppose the storageupmaster possibly, are putting lock times on
other tables.
$ log2sql --version
log2sql, version v0.8.1 (branch: master, revision: c834aaf)
build user: rcowham@perforce.com
build date: 2020-09-05T19:01:35+0100
go version: go1.13.4
....
--- db.workingx
--- total lock wait+held read/write 0ms+31ms/0ms+1856ms
--- max lock wait+held read/write 0ms+31ms/0ms+1855ms
--- db.change
--- total lock wait+held read/write 7ms+1ms/2337ms+0ms
--- max lock wait+held read/write 7ms+1ms/2337ms+0ms
--- storageup/storageup(R)
--- total lock wait+held read/write 0ms+1635446ms/0ms+0ms
startTime endTime running user cmd pid tableName maxReadHeld maxWriteHeld totalReadWait totalReadHeld totalWriteWait
0 2020/10/13 16:55:29 2020/10/13 17:22:45 184 supadhyayula user-shelve 44149 change 1 0 0 1635446 0
- Status
- Open
- Project
- perforce-software-log-analyzer
- Severity
- B
- Reported By
- scott_common
- Reported Date
- 4 years ago
- Modified By
- scott_common
- Modified Date
- 4 years ago
- Owned By
- scott_common
- Type
- Bug
Log in to comment