不幸的是，如果所需数据量远大于内核缓冲区大小的话，这个方法本身可能成为一个性能瓶颈。
Unfortunately, this approach itself can become a performance bottleneck if the size of the data requested is considerably larger than the kernel buffer size.
日志缓冲区大小是由LOGBUFSZ数据库参数定义的。
The log buffer size is defined by the LOGBUFSZ database parameter.
如果超过这个缓冲区大小，数据库服务器会丢弃保存的数据。
If this buffer size is exceeded, the database server discards saved data.
可以更改缓冲区大小来限制这种上溢，从而提高数据对队列管理器的可用性。
You can change the buffer sizes to limit this overspill so that data is more readily available to the queue manager.
tcp _ sendspace——控制内核中用于缓冲应用程序数据的缓冲区空间大小。
Tcp_sendspace -this controls how much buffer space in the kernel is used to buffer application data.
另一个问题在于，精确字段仅指定一个参数的最大长度，但是缓冲区需要针对组合起来的数据的最大尺寸调整大小。
Another problem is that precision fields only specify the maximum size of one parameter, but buffers need to be sized for the maximum size of all data combined instead.
对于具有许多更新工作负载的数据库系统而言，下面日志缓冲区的默认大小(LOGBUFSZ)通常都太小。
The default size of the log buffer (LOGBUFSZ) below is normally too small for database systems with many update workloads.
假设发现缓冲区大小和提供实际的数据都需要执行相同的算法。
Assume that discovering the buffer sizes and providing the actual data require the execution of the same algorithm.
如果创建表的表空间的页面大小不合适，或者应该用另一个缓冲区池访问表，就可能需要执行这种数据转移。
This may become necessary if the table was created in a tablespace with an inadequate page size or when a separate bufferpool should be used for accessing the table.
为避免去发现数据大小，数据使用者可以分配一个任意大小的缓冲区。
To avoid discovering data size, the consumer can allocate a buffer of an arbitrary size.
根据跟踪量、缓冲区大小和输出设备的带宽，可以将多个缓冲区分配给给定的线程，从而与生成跟踪数据的速度相匹配。
Depending on trace volume, buffer size, and the bandwidth of the output device, multiple buffers might be allocated to a given thread to keep pace with trace data that is being generated.
缓冲区的大小是由AUDIT _ BUF_SZ这个数据库管理器配置参数决定的。
The size of the buffer is determined by the AUDIT_BUF_SZ database manager configuration parameter.
对于缓冲区处理，MFC 将大小为零的数据请求当作无操作来对待，所以即使没有数据可读取了，也可以继续发出请求。
For the buffer processing, the MFC treats a zero-size data request as a no-op, so I can go ahead and issue requests even if there is no data to read.
定义日志缓冲区大小的数据库配置参数为LOGBUFSZ。
The database configuration parameter that defines the size of the log buffer is called LOGBUFSZ.
这之所以会成为问题是因为，虽然缓冲区的大小一经分配就不会变化，但是缓冲区中剩余的空间量会在每次添加或删除数据时发生变化。
That's a problem because, while a buffer's size doesn't change once it's allocated, the amount of space left in the buffer changes every time data is added or removed.
数据库管理器参数rqrioblk控制着联邦系统与数据源之间的通信缓冲区的大小。
The database manager configuration parameter rqrioblk controls the size of the communication buffer between the federated system and the data sources.
审计缓冲区大小(audit _ buf_sz)：该参数指定审计数据库时使用的缓冲区的大小。
Audit buffer size (audit_buf_sz) : This parameter specifies the size of the buffer used when auditing the database.
这个标记允许您查看内核malloc统计数据；mbuf内存请求，包括缓冲区大小、CPU的使用和故障(参见清单6)。
This flag allows you to view the Kernel malloc statistics; the mbuf memory requests, including the size of the buffers, the amount in use and the failures by CPU (see Listing 6).
对应用数据分块，使得数据块大小符合通信子网mtu有效负载的要求，避免IP层分片需要重新分配缓冲区、计算校验和以及数据复制的费时操作。
Therefore, it can reduce one time data handling, 3 divide application data into blocks that content the demand of effective load of communication subnet MTU to avoid IP fragments.
对应用数据分块，使得数据块大小符合通信子网mtu有效负载的要求，避免IP层分片需要重新分配缓冲区、计算校验和以及数据复制的费时操作。
Therefore, it can reduce one time data handling, 3 divide application data into blocks that content the demand of effective load of communication subnet MTU to avoid IP fragments.
应用推荐