Help with a stat setting - EnableNLBforStats (dbscontrol)

Database
Teradata Employee

Help with a stat setting - EnableNLBforStats (dbscontrol)

We have a Customer asking this question:

-----Original Message-----

From: owner-tscs-sft-team@lists.teradata.com [mailto:owner-tscs-sft-team@lists.teradata.com] On Behalf Of Gamble, Jeanette

Sent: Wednesday, October 15, 2014 7:49 PM

To: 'tscs-sft-team@lists.teradata.com'

Subject: Help with a stat setting

Anyone use this setting

WISEPROD-- FALSE

  211.  EnableNLBforStats           = FALSE

Do you know why it helps being set to true? Risk/impact?

Can't get much info.

Thx

----------------------------------------------------

The Customer got the following response from one of the other Customers on the SFT:

---------------------------

From: Sanchez, Idrike [mailto:idrike.sanchez@united.com]

Sent: Wednesday, October 15, 2014 09:52 PM

To: Gamble, Jeanette (Enterprise Infrastructure); 'tscs-sft-team@lists.teradata.com' <tscs-sft-team@lists.teradata.com>

Subject: RE: Help with a stat setting - EnableNLBforStats

I have this set to TRUE on our current box.

I have an old email that says:

      169. EnableNLBforStats - This field is used to Enable the Node level

      buffering

           for COLLECT STATS requests.                                          

           The value of false means NLB is disabled. (Default)                  

           The value of true means NLB is enabled.

          Default: ==> FALSE

          Reference Article: ==> DR143506

          Recommended setting: ==> Default

          Tpareset Required? ==> NO

I looked up the DR mentioned, but it does not look to be customer viewable.

The DR app says:

This report was generated on 10/15/2014 at 19:49:24.

Criteria:

  • DR 143506

Returned records: 1 

App Code

Number

Abstract

Status

Type

Product

Component

Symptom Description

Open Date

Last Update Date

RFC Status

RFC Disposition

Found In Release

Target Release

Fixed In Release

Workaround

Tech Alert

DR

143506

PERF: Node Level Buffering causes regression on small system/large AMP configurations

COMPLETE

Defect

DBS

AMP

On a Smaller system with Large AMP configuration (i.e number of nodes are less and the number of AMPs per node are more than 25) collect stats is showing upto 60% regression.

HIDE

2010/06/23

2011/03/29

12.00.03.003

12.00.03.010 13.00.00.021

14.10.00.00 14.00.01.01 14.00.00.00 13.10.03.01 13.10.02.517 13.10.02.01 13.10.01.509 13.10.01.05 13.10.01.02 13.10.01.01 13.10.00.306 13.10.00.09 13.10.00.06 13.10.00.00 13.00.01.01 13.00.00.25 13.00.00.21 12.00.03.10

 

..kiki..

------------------------------------

I did a search here and don't find any references to this subject, so wanted to post this exchange and see if anybody has any comments to add to this discussion.