Pi interface for Bailey Infi90

Primary and Secondary Memory Buffer Size (Bytes)

Download 1.41 Mb.

View original pdf

Page	41/59
Date	25.06.2022
Size	1.41 Mb.
	#59078

1 ... 37 38 39 40 41 42 43 44 ... 59

PI BaInfi90 1.8.4.9

Send rate (milliseconds)
PI Interface for Bailey Infi90 53 Maximum transfer objects
Event Queue File Size (Mbytes)
Event Queue Path

Primary and Secondary Memory Buffer Size (Bytes)
This is a key parameter for buffering performance. The sum of these two memory buffer sizes must be large enough to accommodate the data that an interface collects during a single scan. Atypical event with a Float point type requires about 25 bytes. If an interface writes data to 5,000 points, it can potentially send 125,000 bytes (25 * 5000) of data in one scan. As a result, the size of each memory buffer should be 62,500 bytes. The default value of these memory buffers is 32,768 bytes. OSIsoft recommends that these two memory buffer sizes should be increased to the maximum of 2000000 for the best buffering performance.
Send rate (milliseconds)
Send rate is the time in milliseconds that PIBufss waits between sending up to the Maximum
transfer objects (described below) to the PI Server. The default value is 100. The valid range is 0 to 2,000,000.

PI Interface for Bailey Infi90
53
Maximum transfer objects
Maximum transfer objects is the maximum number of events that PIBufss sends between each Send rate pause. The default value is 500. The valid range is 1 to 2,000,000.
Event Queue File Size (Mbytes)
This is the size of the event queue files. PIBufss stores the buffered data to these files. The default value is 32. The range is 8 to 131072 (8 to 128 Gbytes). Please seethe section entitled "Queue File Sizing" in the PIBufss.chm file for details on how to appropriately size the event queue files.
Event Queue Path
This is the location of the event queue file. The default value is
[PIHOME]\DAT
For optimal performance and reliability, OSIsoft recommends that you place the PIBufss event queue files on a different drive/controller from the system drive and the drive with the Windows paging file. (By default, these two drives are the same)
Bufserv
For Bufserv, the paragraphs below describe the settings that may require user intervention. Please contact OSIsoft Technical Support for assistance in further optimizing these and all remaining settings.

Download 1.41 Mb.

Share with your friends:

1 ... 37 38 39 40 41 42 43 44 ... 59