[MarkLogic Dev General] Slow estimate

[Michael Blakeley]

Emile,

That estimate should be nearly instantaneous. It is possible that your 
machine is running out of memory, or swapping.

I recommend that you contact support at marklogic.com. The first thing they 
will ask you for is a "full support dump": you can generate this using 
the MarkLogic Admin server (usually on port 8001), via the "Support" tab.

thanks,
-- Mike

> I just received an unexpectedly slow response to an estimate
> on a database with 9.87 million documents of about 5kb each.
> 
> Here's the query which took over 2 minutes to return:
> 
> xdmp:estimate(//Journal[count(ISSN) > 1]), xdmp:query-meters()
> 
> I want to find out how many documents have a <Journal> with more
> than one <ISSN> sub-element.
> 
> The server is a 2 * dual core Opteron with 16GB of RAM running RE3 
> and Marklogic 3.1 .
> 
> I'm expecting a very small or zero estimate, but I can't confirm 
> this because using the 'count' function takes too long.
> 
> Is there anything I should be doing different to get a faster
> and more accurate estimate, or a faster count?
> 
> Please see below the output from query-meters which shows the 
> result from the above query:
> 
> <results warning="more than one node">
> 9870000
> <qm:query-meters
> xsi:schemaLocation="http://marklogic.com/xdmp/query-meters
> query-meters.xsd">
> <qm:elapsed-time>PT2M32.28S</qm:elapsed-time>
> <qm:requests>1</qm:requests>
> <qm:list-cache-hits>9</qm:list-cache-hits>
> <qm:list-cache-misses>0</qm:list-cache-misses>
> <qm:in-memory-list-hits>0</qm:in-memory-list-hits>
> <qm:expanded-tree-cache-hits>0</qm:expanded-tree-cache-hits>
> <qm:expanded-tree-cache-misses>0</qm:expanded-tree-cache-misses>
> <qm:compressed-tree-cache-hits>0</qm:compressed-tree-cache-hits>
> <qm:compressed-tree-cache-misses>0</qm:compressed-tree-cache-misses>
> <qm:in-memory-compressed-tree-hits>0</qm:in-memory-compressed-tree-hits>
> <qm:value-cache-hits>0</qm:value-cache-hits>
> <qm:value-cache-misses>0</qm:value-cache-misses>
> <qm:regexp-cache-hits>0</qm:regexp-cache-hits>
> <qm:regexp-cache-misses>0</qm:regexp-cache-misses>
> <qm:link-cache-hits>0</qm:link-cache-hits>
> <qm:link-cache-misses>0</qm:link-cache-misses>
> <qm:fragments-added>0</qm:fragments-added>
> <qm:fragments-deleted>0</qm:fragments-deleted>
> <qm:fs-program-cache-hits>1</qm:fs-program-cache-hits>
> <qm:fs-program-cache-misses>0</qm:fs-program-cache-misses>
> <qm:db-program-cache-hits>0</qm:db-program-cache-hits>
> <qm:db-program-cache-misses>0</qm:db-program-cache-misses>
> <qm:fs-main-module-sequence-cache-hits>0</qm:fs-main-module-sequence-cac
> he-hits>
> <qm:fs-main-module-sequence-cache-misses>0</qm:fs-main-module-sequence-c
> ache-misses>
> <qm:db-main-module-sequence-cache-hits>0</qm:db-main-module-sequence-cac
> he-hits>
> <qm:db-main-module-sequence-cache-misses>0</qm:db-main-module-sequence-c
> ache-misses>
> <qm:fs-library-module-cache-hits>0</qm:fs-library-module-cache-hits>
> <qm:fs-library-module-cache-misses>0</qm:fs-library-module-cache-misses>
> <qm:db-library-module-cache-hits>0</qm:db-library-module-cache-hits>
> <qm:db-library-module-cache-misses>0</qm:db-library-module-cache-misses>
> <qm:fragments/>
> <qm:documents/>
> </qm:query-meters>
> </results>