Selecting the input buffer size.
选择输入缓冲区的大小。
The minimum buffer size is 1 megabyte.
缓冲区大小最少也要达到 1 兆字节。
Increase the log buffer size to 256 pages or larger.
将日志缓冲区大小增加到256个页面或更大。
The buffer size can be specified in bytes or megabytes.
可以按字节或兆字节来指定缓冲区的大小。
The buffer option is -bufsize to set the buffer size in bits.
缓冲选项 -bufsize 用来设置缓冲区的大小,单位为比特。
When you specify a buffer size, the value must be a power of 2.
当指定一个缓冲区大小时,该值必须是2的幂。
For example, a value of 1048576 specifies a buffer size of 1mb.
例如,值1048576指定缓冲区大小为1MB。
For example, a value of 1048576 specifies a buffer size of 1 MB.
例如,值1048576指定缓冲区大小为1MB。
The log buffer size is defined by the LOGBUFSZ database parameter.
日志缓冲区大小是由LOGBUFSZ数据库参数定义的。
If this buffer size is exceeded, the database server discards saved data.
如果超过这个缓冲区大小,数据库服务器会丢弃保存的数据。
Log buffer size (this also applies to non-persistent events and actions).
Logbuffer size(也适用于非持久性事件和动作)。
If you omit this parameter, Tprof will use the default buffer size of five Megabytes.
如果您忽略了这一参数,则Tprof将使用默认的缓冲区大小——5MB。
This parameter sets the buffer size for map-side sorting, in units of MB, 100 by default.
这个参数设置用于 map 端排序的缓冲区大小,单位是MB,默认值是 100。
If your network is reliable, try increasing the buffer size from the default (8000) to 64000.
如果您的网络可靠,尝试将缓冲区大小从默认的8000提高到64000。
Set the catalog cache, package cache, and log buffer size to an appropriate size to improve performance.
要设置大小适当的目录缓存器、包缓存器和日志缓冲区以提高性能。
This significantly improves performance when the requested data amount is less than the kernel buffer size.
这在所需数据量小于内核缓冲区大小时极大地提高了性能。
For performance reasons, the trace facility does not allow you to change the trace buffer size dynamically.
由于性能的原因,跟踪功能不允许动态更改跟踪缓冲区的大小。
Audit buffer size (audit_buf_sz) : This parameter specifies the size of the buffer used when auditing the database.
审计缓冲区大小(audit _ buf_sz):该参数指定审计数据库时使用的缓冲区的大小。
If you are parsing documents under 2 KB in size, you may want to choose an input buffer size that's smaller than 2 KB.
如果解析的文档小于2KB,也可以选择小于2 KB的输入缓冲区大小。
For small documents (generally less than 4 KB), sticking with the default buffer size should give you good performance.
对于小型文档(一般小于4KB),使用默认缓冲区大小就能取得很好的性能。
The sample program does not check for EVENT_OVERFLOW since it specifies an INFO_LVL of 1 and USES the default buffer size of 4k.
示例程序并不检查EVENT_OVERFLOW,因为它指定info_lvl为1并使用默认缓冲区大小4k。
The default and minimum trace buffer sizes depend on the version of DB2, and the maximum trace buffer size depends on the platform.
缓冲区的默认大小和最小值取决于DB2的版本,跟踪缓冲区的最大值取决于平台。
The POSIX 1003.1 standard defines strerror_r , which accepts a pointer to a buffer and a buffer size in addition to the error value.
POSIX 1003.1标准定义strerror _ r,该函数除接受错误值之外,还接受缓冲区中的指针和缓冲区大小。
The choice of buffer size can greatly affect performance when auditing is started since many records may be written to the audit log.
缓冲区大小的选择将在很大程度上影响审计的性能,因为可能要将很多记录写到审计日志中。
Some performance tests have showed that increasing this input buffer size improves performance when parsing documents larger than 2 KB.
一些性能测试表明,解析大于2KB的文档时增加输入缓冲区的大小能够提高性能。
You might also have a query that runs against a very large table that USES the same buffer pool and involves reading more pages than the total buffer size.
假设有一个针对非常大的表运行的查询,它使用同一个缓冲池并且需要读取比总的缓存区大小还多的页。
Unfortunately, this approach itself can become a performance bottleneck if the size of the data requested is considerably larger than the kernel buffer size.
不幸的是,如果所需数据量远大于内核缓冲区大小的话,这个方法本身可能成为一个性能瓶颈。
Collection options include turning a trace on or off; specifying the trace buffer size; specifying or changing trace options; dumping a trace; and clearing the trace buffer.
收集选项包括打开或关闭跟踪;指定跟踪缓冲区大小;指定或更改跟踪选项;转储跟踪信息;以及清除跟踪缓冲区。
The overall buffer size has a significant effect on DB2 performance, because a large number of pages can significantly reduce I/O, which is the most time-consuming operation.
整个缓冲区大小对DB2性能有巨大影响,这是因为大量的页可以显著地减少I/O这一最耗时的操作。
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.
根据跟踪量、缓冲区大小和输出设备的带宽,可以将多个缓冲区分配给给定的线程,从而与生成跟踪数据的速度相匹配。
应用推荐