The MDEX Engine cache has been improved to allow it better handle performance requirements of applications with a high number of threads.
Three new columns have been added to the Cache tab in the MDEX Engine Stats page. The data in these columns can be useful to you if you need to analyze and tune the cache or re-design the front-end application to improve performance of the MDEX Engine.
These new columns are added to the Cache tab of the MDEX Engine Stats page:
“Number of rejections”. Examining this column is useful if you want to see whether you need to increase the amount of memory used for the MDEX cache. Counts greater than zero in this column indicate that the cache is undersized and you may want to increase it.
“Number of reinsertions”. Examining this column is useful if you want to examine your queries for similarities and improve performance by considering the redesign of the front-end application. Large counts in the "Number of reinsertions" column indicate that simultaneous queries are computing the same values, and it may be possible to improve performance by sequencing queries, if the application design permits.
"Total reinsertion time". Examining this column is useful for quantifying the overall performance impact of queries that contribute to the "Number of reinsertions" column. This column represents the aggregated time that has been spent calculating identical results in parallel with other queries. This is the amount of compute time that potentially can be saved by sequencing queries in a re-design of the front-end application.
