Jaspreet,

Have you actually reproduced the slow query in queryConsole and run it using the
"profile" button? This should show the function calls that are taking the most
time - high "%shallow" numbers indicate that a function is taking a lot of time.

Then, if the slow function calls are xpath or search functions, we can then
advise you on how to turn on query profiling (using xdmp:plan(), for instance).

Yours, Damon

From: gene...@developer.marklogic.com
[mailto:gene...@developer.marklogic.com] On Behalf Of JASPREET SINGH Sent: Tuesday, February 28, 2012 2:55 AM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] SVC:EXTIME -- Time limit exceeded

Thanks michael for your suggestion. As you have mentioned to post the code, my
code makes so much of internal function calls to different modules. So, I think
posting the code would not be helpful. I m trying profiling to different
functions but not reaching to the root cause. Should I use the same approach or
you have some experiences to share?

Thanks and Regards, Jaspreet Singh On Tue, Feb 28, 2012 at 11:17 AM, Michael Blakeley
<mi...@blakeley.com<mailto:mi...@blakeley.com>> wrote: First, profile your code to figure out which bit is taking so long. Then rewrite
it so it's faster. Repeat until you are happy with performance.

If you post code and profiler output here, you might get some suggestions.

-- Mike

On 27 Feb 2012, at 21:28 , JASPREET SINGH wrote: