[MarkLogic Dev General] Number of threads for ML app
mike at blakeley.com
Wed Aug 22 07:43:10 PDT 2012
Your workload should guide you to the correct number of threads. I would start with 2x cores, because of network latency.
You may also want to consider a load balancer and/or reverse-proxy in front of MarkLogic. The benefits from operational flexibility should be clear. But in the case where you need to handle large numbers of requests from distant, high-latency clients, this gives you a cheap place to buffer them up. If your clients are few and well-connected, this is less of an issue. But the operational flexibility is still useful.
On 22 Aug 2012, at 04:33 , Danny Sinang wrote:
> Our ML server is hosted by a machine with 16 cores with hypterthreading so it looks like it has 32 cores total.
> Our main ML app is configured to use 32 threads with a backlog of 256 . Should we stick to this setting or can we bump up the number of threads to handle more requests simultaneously ?
> My colleague thinks we should match the number of ML threads to the number of threads accepted by the application servers call ML services. I, however, think we can't and shouldn't go beyond 32 because that's the actual number of cores our machine has.
> Would appreciate any advice on this matter.
> General mailing list
> General at developer.marklogic.com
More information about the General