You should use this low-level tracing only as a last resource for troubleshooting. Enabling this attribute substantially degrades performance. Setting a value that is too small can block indexing operations.Įnables low-level trace information for indexing operations. ![]() Increasing the queue-size value increases the amount of memory that is used during indexing operations. Maximum number of elements each queue can hold. For optimum results, do not set a value for queue-count that is larger than the value for thread-pool-size. Increasing the number of queues will lead to an increase of indexing throughput, but only if the bottleneck is CPU. Each queue holds a batch of modifications that is applied to the index and queues are processed in parallel. Number of internal queues to use for each indexed type. Number of threads that execute write operations to the index. When used in combination with the max-buffered-entries attribute, a flush occurs for whichever event happens first. For faster indexing performance you should set this attribute instead of max-buffered-entries. Large values result in faster indexing but use more memory. Maximum amount of memory that can be used for buffering added entries and deletions before they are flushed to the index storage. When used in combination with the ram-buffer-size attribute, a flush occurs for whichever event happens first. Maximum number of entries that can be buffered in-memory before they are flushed to the index storage. Because operation is costly, small values should be avoided. ![]() Index writer configuration attributes AttributeĪmount of time, in milliseconds, that index changes that are buffered in memory are flushed to the index storage and a commit is performed. ![]() Continuous queries and Infinispan performance Querying caches from Infinispan Console and CLI Querying caches from Hot Rod Java clients
0 Comments
Leave a Reply. |