I do a search with three subqueries only interested in the category of the property:
[[property::<q>[[Category:X]]</q>]] (93 members, 1 subcategory) [[property::<q>[[Category:Y]]</q>]] (45 members, no subcategories) [[property::<q>[[Category:Z]]</q>]] (122 members, 3 subcategories) And it makes mysqld chug CPU for twenty minutes. Now, I'd think I was just asking too much from it and including too many subqueries, but even two of the subqueries (Y and Z) above is enough to make it choke for about five minutes. One category (X) is done in just a couple seconds. Meanwhile, the same searches on SMW 0.7 are instantaneous or take no more than a second or two. (Same server under same conditions, same data.) If there's a quick answer to why this might be happening and how I can fix it, let me know, but I'll be trying to look at it in the meantime. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Semediawiki-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
