Cache size: the size of the cache.
Cache size:缓存的大小。
文档缓存大小。
In fact, there is only one: the cache size.
事实上只有一个:缓存大小。
The non-computational file cache size in MB
非计算文件缓存大小,以 MB 为单位
Set XSL cache size to the desired number.
将XSLcache size 设置为一个理想的数值。
The percentage of file cache size against the true memory size
文件缓存大小占实际内存大小的百分比
To change the cache size, use the mqsichangeproperties command.
修改高速缓存的大小的方法是使用 mqsichangeproperties 命令。
The cache size specifies the maximum number of entries that the cache can hold.
缓存大小指定缓存可以容纳的最大条目数。
The data source statement cache size can be tuned using a few different methods.
可以使用一些不同的方法来调优数据库语句缓存大小。
If the cache size is less than the set value, Lotus Quickr does not recycle the cache.
如果缓存大小小于此设置值,LotusQuickr无法回收缓存。
The current maximum theoretical cache size is 2gb. The cache size is limited by the following factors.
当前缓存大小的理论最大值是2GB。
You should specify a cache size of about 50mb to ensure that there is enough space for all the classes.
应该将缓存的大小指定为大约50MB,从而确保能够存储所有的类。
The hit ratio is a function of the cache size, the amount of underlying data, and the data access pattern.
命中率与缓存大小、底层数据的数量和数据访问模式有关。
If the cache size is greater than the setting, the Lotus Quickr server recycles the cache size to the set value.
如果缓存大小大于设置,LotusQuickr服务器将回收设置值大小的缓存。
For now, leave the "Cache size" and "default priority" with their default values of 2000 and 1, respectively.
眼下,请将“Cache size”和“Defaultpriority”分别保留为缺省值2000和1。
Data source statement cache size specifies the number of prepared JDBC statements that can be cached per connection.
数据源语句缓存大小指定每次连接可以缓存的经过准备的jdbc语句的数量。
The size you specify for the statement cache size should be relatively large. Typically this is in the range of 100-200.
您为语句缓存指定的大小应当相对较大,一般在100到200之间。
The size you specify for the statement cache size should be relatively large. Typically, this is in the range of 100-200.
您为语句缓存指定的大小应当相对较大,一般在100到200之间。
Note that if this variable is set too large, the Lotus Quickr server spends more resources to handle the larger cache size.
注意,如果变量设置太大,LotusQuickr服务器需要消费更多资源才能处理更大的缓存大小。
You specify cache size using the parameter -Xscmx[k|m|g]; this parameter only applies if a new cache is created by the JVM.
使用参数-Xscmx[k|m|g]指定缓存的大小;这个参数只应用于JVM创建新缓存的情况。
Once you've set the initial options and configured the directory and cache size you want, there's no need to change anything.
一旦设置了初始化选项并配置了期望的目录和高速缓存大小,就不需要再做任何改动。
The value is not a number of resulting entries, but more of an indicator of how big the cache size for the results should be.
此值不是所得到的条目数,而是指示结果缓存大小的值。
Therefore, when tuning the cache size for your environment, allocate sufficient in-memory and disk space for the cache entries.
因此,在为您的环境优化缓存大小时,请为缓存项分配足够的内存和磁盘空间。
Thus, performance is best if the cache size is set to the maximum number of active instances expected during a typical workload.
因此,在典型的工作负载过程中,如果将缓存大小设置为预期的最大活动实例数,则性能是最佳的。
Benchmark tests are not perfect, but are a better indicator of microprocessor speed than clock rate or cache size specifications.
对双核内存测评结果不是很好,但是微处理器处理速度和时钟频率或是缓存空间相比要很好的多。
Statistics such as the cache size, used entries, cache hits and misses, and many more provide a good overview of their usage patterns.
诸如缓存大小、已使用的条目、缓存命中率和未命中率之类的统计数据以及更多的数据可以很好地概述缓存的使用模式。
Check that the cache size is sufficiently large and that the cache hit ratio is high for each of the dynamic SQL statements being executed.
对于每个被执行的动态sql语句,请检查高速缓存是否足够大且高速缓存的命中率是否较高。
Looking back at the chart in Figure 11, before tuning the data source statement cache size, the number of statements discarded was over 1.7 million.
回过头来看图9中的表,在调优数据源语句缓存大小之前,被丢弃的语句的数量超过170万条。
Looking back at the chart in Figure 11, before tuning the data source statement cache size, the number of statements discarded was over 1.7 million.
回过头来看图9中的表,在调优数据源语句缓存大小之前,被丢弃的语句的数量超过170万条。
应用推荐