Okay, I will benchmark it then, good idea!



> On 25.04.2014, at 18:36, Tobi Knaup <notifications@github.com> wrote:
> 
> In src/main/scala/mesosphere/marathon/MarathonScheduler.scala:
> 
> > @@ -73,12 +73,16 @@ class MarathonScheduler @Inject()(
> >        try {
> >          log.fine("Received offer %s".format(offer))
> >  
> > -        // TODO launch multiple tasks if the offer is big enough
> > -        val app = taskQueue.poll()
> > +        val apps = taskQueue.removeAll()
> Yes, it'll be a bit more complex. The reason I mention it is because all callbacks in the scheduler interface are single threaded so on a large/busy cluster this could stall things. You want to do as little as possible in any of the callbacks. It would be great to write a benchmark for resourceOffers()
> …
> —
> Reply to this email directly or view it on GitHub.