DB2 - L

• For systems in which deadlocking is not a problem, have deadlock detection run less frequently for the best performance and concurrency (but do not choose a value greater than 5 seconds).

"

We have a very busy computer (most of the time it's over 95% and on 100% frequently).
On Average, we have about 10-15 deadlocks per day.

My gut feeling is that this parameter should be set higher, what do you think?

The impact of the DEADLOCK check is in 2 areas:

1. Application is waiting while the check is done.

more checks means higher lock wait time.

2. DB2 itself is wasting CPU on too frequent checks.

The big question is how do I measure the impact of changing this parameter.

For item 1, do I need to check QWACAWTL/QTXASLAT/ other?

Is there a way to measure item 2 (DB2 CPU consumed for Deadlock DETECTION)?

Thanks,
Shay.

• For systems in which deadlocking is not a problem, have deadlock detection run less frequently for the best performance and concurrency (but do not choose a value greater than 5 seconds).

"

We have a very busy computer (most of the time it's over 95% and on 100% frequently).
On Average, we have about 10-15 deadlocks per day.

My gut feeling is that this parameter should be set higher, what do you think?

The impact of the DEADLOCK check is in 2 areas:

1. Application is waiting while the check is done.

more checks means higher lock wait time.

2. DB2 itself is wasting CPU on too frequent checks.

The big question is how do I measure the impact of changing this parameter.

For item 1, do I need to check QWACAWTL/QTXASLAT/ other?

Is there a way to measure item 2 (DB2 CPU consumed for Deadlock DETECTION)?

Thanks,
Shay.

• For systems in which deadlocking is not a problem, have deadlock detection run less frequently for the best performance and concurrency (but do not choose a value greater than 5 seconds).

"

We have a very busy computer (most of the time it's over 95% and on 100% frequently).
On Average, we have about 10-15 deadlocks per day.

My gut feeling is that this parameter should be set higher, what do you think?

The impact of the DEADLOCK check is in 2 areas:

1. Application is waiting while the check is done.

more checks means higher lock wait time.

2. DB2 itself is wasting CPU on too frequent checks.

The big question is how do I measure the impact of changing this parameter.

For item 1, do I need to check QWACAWTL/QTXASLAT/ other?

Is there a way to measure item 2 (DB2 CPU consumed for Deadlock DETECTION)?

Thanks,
Shay.

• For systems in which deadlocking is not a problem, have deadlock detection run less frequently for the best performance and concurrency (but do not choose a value greater than 5 seconds).

"

We have a very busy computer (most of the time it's over 95% and on 100% frequently).
On Average, we have about 10-15 deadlocks per day.

My gut feeling is that this parameter should be set higher, what do you think?

The impact of the DEADLOCK check is in 2 areas:

1. Application is waiting while the check is done.

more checks means higher lock wait time.

2. DB2 itself is wasting CPU on too frequent checks.

The big question is how do I measure the impact of changing this parameter.

For item 1, do I need to check QWACAWTL/QTXASLAT/ other?

Is there a way to measure item 2 (DB2 CPU consumed for Deadlock DETECTION)?

Thanks,
Shay.

• For systems in which deadlocking is not a problem, have deadlock detection run less frequently for the best performance and concurrency (but do not choose a value greater than 5 seconds).

"

We have a very busy computer (most of the time it's over 95% and on 100% frequently).
On Average, we have about 10-15 deadlocks per day.

My gut feeling is that this parameter should be set higher, what do you think?

The impact of the DEADLOCK check is in 2 areas:

1. Application is waiting while the check is done.

more checks means higher lock wait time.

2. DB2 itself is wasting CPU on too frequent checks.

The big question is how do I measure the impact of changing this parameter.

For item 1, do I need to check QWACAWTL/QTXASLAT/ other?

Is there a way to measure item 2 (DB2 CPU consumed for Deadlock DETECTION)?

Thanks,
Shay.

• For systems in which deadlocking is not a problem, have deadlock detection run less frequently for the best performance and concurrency (but do not choose a value greater than 5 seconds).

"

We have a very busy computer (most of the time it's over 95% and on 100% frequently).
On Average, we have about 10-15 deadlocks per day.

My gut feeling is that this parameter should be set higher, what do you think?

The impact of the DEADLOCK check is in 2 areas:

1. Application is waiting while the check is done.

more checks means higher lock wait time.

2. DB2 itself is wasting CPU on too frequent checks.

The big question is how do I measure the impact of changing this parameter.

For item 1, do I need to check QWACAWTL/QTXASLAT/ other?

Is there a way to measure item 2 (DB2 CPU consumed for Deadlock DETECTION)?

Thanks,
Shay.

• For systems in which deadlocking is not a problem, have deadlock detection run less frequently for the best performance and concurrency (but do not choose a value greater than 5 seconds).

"

We have a very busy computer (most of the time it's over 95% and on 100% frequently).
On Average, we have about 10-15 deadlocks per day.

My gut feeling is that this parameter should be set higher, what do you think?

The impact of the DEADLOCK check is in 2 areas:

1. Application is waiting while the check is done.

more checks means higher lock wait time.

2. DB2 itself is wasting CPU on too frequent checks.

The big question is how do I measure the impact of changing this parameter.

For item 1, do I need to check QWACAWTL/QTXASLAT/ other?

Is there a way to measure item 2 (DB2 CPU consumed for Deadlock DETECTION)?

Thanks,
Shay.