From: Xma M. <mon...@gm...> - 2012-04-01 08:41:41
|
i am learning a lot about eXist and how it uses queries and the query cache. im studying how it impacts performance on high concurrency applications. when i have something more concise to share about this, i will post my findings here. in the mean time, can anyone weigh in on this question? in conf.xml, is there a reason that i should not set the @timeout-check-interval on the <query-pool/> to -1? i have tested and if the XQuery is modified, the change is detected and the query is forcibly recompiled. however, if no change has actually occurred, i dont want my compiled queries to time-out and be recycled and have to be recompiled again. in the middle of high concurrency, that's an expensive (and potentially blocking) operation. the current time-out interval is (@timeout) is set to 120000 (2 minutes i think). anyone know reason that i should not do this? thanks! xMonkey |