University of North Texas Computing & IT Center
http://itsm.unt.edu/
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Rick Cook
Sent: Thursday, April 14, 2011 1:26 PM
To: arslist@ARSLIST.ORG
Subject: Re: 7.6.04 Next Request ID block size
**
To minimize
BMC engineering validated my findings. Unless you are on a very busy server
with large numbers of submits against the same form, there is no performance
benefit to any setting greater than 1.
Rick
On Apr 14, 2011 1:26 PM, remedyr...@gmail.com wrote:
> To minimize the number of 'get' operations fo
when you have the BMC tools it makes a difference..
BMC portal
BMC impact
BMC Event
BMC performance
BMC bladelogic Client Automation
BMC Bladelogic Server Automation.
On Thu, Apr 14, 2011 at 2:26 PM, Rick Cook wrote:
> **
>
> To minimize the number of 'get' operations for Entry IDs. Unfortuna
To minimize the number of 'get' operations for Entry IDs. Unfortunately, my
own testing showed that unless you have multiple sources (i.e. NMS) creating
many records at the same time, it actually slowed performance rather than
improving it.
Most people should just leave it set to 1.
Rick
On Apr
e 1000 would be.
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Chowdhury, Tauf
Sent: Thursday, April 14, 2011 11:49 AM
To: arslist@ARSLIST.ORG
Subject: 7.6.04 Next Request ID block size
**
Does anyone know why BMC recommends setting the next r
Does anyone know why BMC recommends setting the next request ID block
size to 100?
Tauf Chowdhury | Forest Laboratories, Inc.
Analyst, Service Management
Informatics-Infrastructure
Office: 631.858.7765
Mobile:646.483.2779
*
6 matches
Mail list logo
