The server is keeping some idle threads active to handle incoming requests. 
That's meant to improve performance. A thread may also spend a small amount of 
time cleaning up after a request completes, but this should be minimal.

If you're trying to track down a latency issue I think you should look 
elsewhere. Have you profiled your requests yet?

-- Mike

> On 9 Jan 2015, at 06:17 , <gnanaprakash.bodire...@cognizant.com> 
> <gnanaprakash.bodire...@cognizant.com> wrote:
> 
> Hi
>  
> I want to understand how threads in app servers work.
>  
> I believe for every request with authentication MarkLogic will show 2 
> threads. But what I see is when we are doing performance testing, MarkLogic 
> is showing 32 threads are being used per node (we have 3 nodes in a cluster) 
> but active thread (requests/updates) as 3-4.
>  
> What’s the difference between Threads and requests/updates. I understand that 
> requests are GET and updates are updating any content (PUT/POST/internal 
> update in GET linked code), the main question is why thread count is more 
> than sum of requests and updates.
>  
> If threads are sockets being opened why they are not getting closed even when 
> the keep alive is just 5 seconds in configuration.
> 
> Can someone help me in understanding this and resolving the latency issue I 
> am facing in my performance testing.
>  
> Regards,
> Gnanaprakash Bodireddy
> 
>  
>  
>  
> This e-mail and any files transmitted with it are for the sole use of the 
> intended recipient(s) and may contain confidential and privileged 
> information. If you are not the intended recipient(s), please reply to the 
> sender and destroy all copies of the original message. Any unauthorized 
> review, use, disclosure, dissemination, forwarding, printing or copying of 
> this email, and/or any action taken in reliance on the contents of this 
> e-mail is strictly prohibited and may be unlawful. Where permitted by 
> applicable law, this e-mail and other e-mail communications sent to and from 
> Cognizant e-mail addresses may be monitored. 
> _______________________________________________
> General mailing list
> General@developer.marklogic.com
> http://developer.marklogic.com/mailman/listinfo/general

_______________________________________________
General mailing list
General@developer.marklogic.com
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to