Thanks for the replies. More resources (separate host) is of course the ideal solution, but I'm trying to explore what we can do in order to share the resources we have at our disposal in a better way. It's possible we could delay some requests, but since this is a site used by a large number of concurrent users, we don't have any control over the distribution of the traffic, and don't really have the luxury to schedule requests for much later (ie run at night).
-Mike On 3/10/2011 4:23 AM, Geert Josten wrote: > Hi Mike, > > To my knowledge MarkLogic Server doesn't support priorities in request queue > nor in task queue. You could apply the approach described by Tim to the > request queue, but spawning them to the task server might be better. You > could also consider having a separate host (or cluster) to take care of long > and/or heavy processes. You could also make some kind of delayed processing > queue, monitored by a schedule that only runs in low traffic times.. > > Kind regards, > Geert > > -----Oorspronkelijk bericht----- > Van: [email protected] > [mailto:[email protected]] Namens Tim Meagher > Verzonden: donderdag 10 maart 2011 2:25 > Aan: 'General MarkLogic Developer Discussion' > Onderwerp: Re: [MarkLogic Dev General] query priority > > I developed pseudo-priorities by polling the number of queued tasks prior to > submitted a lower priority task. The lower priority tasks don't get starved > simply because the task queue is not constantly filled. > > Tim Meagher > > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
