multi layer: now solr's procedure: user query -> solr instance -> show results
i think it maybe simple to some application maybe this procedure fit for: user query -> Master solr query instance -> single solr query instance -> show results master solr query instance: it can define some global field, like score, time, userid which is from every single solr query instance. if so, we can do sort by score, sort by time, filter by userid and so on. To solr user, we not concert about how to do multi query in parrel and merge data . We just care how to define global field, our busness, search ui. test: why we test, we just wanna optimize. how to optimize, which data range i should do something like 'add memory','add solr instance', 'lower filter cache', 'increase query cache', 'less memory so lower autowarm'. now i only depend on my experience to adjust cache, memory, docs num and i do'nt which best i should. so if solr have tools to test or moniter(i read its discuss in pre mail). i read article from wiki ,but i not find something about data range. so i think public tools which test and get data, optimize solr with that data. Public moniter which can tell me real time data change maybe these all solr tomorrow plan, if u have experience with solr, let's talk about it . i like solr. -- regards jl
