m...@blakeley.com
Sent by: general-boun...@developer.marklogic.com
Date: 10/24/2012 06:46PM
Subject: Re: [MarkLogic Dev General] Performance Overhead - cts:sum
Trying http://docs.marklogic.com/cts:sum-aggregate is a good idea. I'll throw
out some others, roughly in order of probability
If you have a range index defined for this (and you definitely should for this
kind of operation) and you're running on 6 or later, try to use
cts:sum-aggregate instead of cts:sum.
-m
On Oct 23, 2012, at 10:20 PM, Abhishek53 S
abhishek5...@tcs.commailto:abhishek5...@tcs.com wrote:
Hi All,
2012 7:21
Aan: MarkLogic Developer Discussion
Onderwerp: [MarkLogic Dev General] Performance Overhead - cts:sum
Hi All,
I am having performance penalty (Average time 23-30 Sec for the first time and
less than 1 sec for next onward hit[which is accecpted]) with cts:sum over one
Trying http://docs.marklogic.com/cts:sum-aggregate is a good idea. I'll throw
out some others, roughly in order of probability and difficulty. Stop whenever
you achieve acceptable response times.
A full 20-30 sec of warmup sounds excessive to me. A large part of the problem
is likely to be
Hi All,
I am having performance penalty (Average time 23-30 Sec for the first time and
less than 1 sec for next onward hit[which is accecpted]) with cts:sum over one
of the element stores valuation information
---
for $id
Developer Discussion
*Onderwerp:* [MarkLogic Dev General] Performance Overhead - cts:sum
Hi All,
I am having performance penalty (Average time 23-30 Sec for the first time
and less than 1 sec for next onward hit[which is accecpted]) with cts:sum
over one of the element stores valuation
