We just finished setting up our first JMS-backed HibernateSearch cluster prototype. The system we built have rather intricate queries and together with these we use Filters for cutting out geographical regions. Moreover, there is a rather high degree of repeated queries and even more repeated regions (the Filter) looking over an hour.

Would it be bad performance-wise to set "hibernate.search.default.refresh" as low as once a minute or so. In other words: Do we lose potential caching in IndexReaders / Filters etc. when an index-refresh is being made? Or is this handled within Hibernate Search in some clever way so that we could as well have a very tight refresh-rate?

Thankful for a quick answer on this before we go too far making loadtests for scenarios that even could be dismissed on a theoretical basis.

Tobias