Alan Berg sent me a nice list of slow-query warnings from the 1.3-SNAPSHOT running on qa20 last month. For regression testing, it's not as good as the results of a repeatable load test, but I do think it's a good way to look for bugs. After some regex-ing and sorting, I've been using it (and our local production pilot log files) as a guide for my 1.4-aimed performance improvements. In case anyone else wants to take a look, I've uploaded it to:
https://docs.google.com/open?id=0B1EI2G0wYLxAVzFZN3o1SHBnZDQ Aside from the Solr tweaking specifics, two things particularly struck me. First, the absence of "message.count.json" warnings happily confirms a query performance fix which got into 1.3. Second, there are a significant number of SparseMapContent complaints about "list children". (This also matches what we see in our 1.1-based production system, although that release has so many pathologically bad Solr queries that the net effect of Sparse isn't much.) SparseMapContent, like the Jackrabbit it replaced, is a hierarchical data store, and so tree-traversal really has to be fast. Best, Ray _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
