aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AURORA-139) Scheduling performance could be vastly improved by caching job information
Date Wed, 29 Jan 2014 18:34:10 GMT
Bill Farner created AURORA-139:
----------------------------------

             Summary: Scheduling performance could be vastly improved by caching job information
                 Key: AURORA-139
                 URL: https://issues.apache.org/jira/browse/AURORA-139
             Project: Aurora
          Issue Type: Story
          Components: Scheduler
            Reporter: Bill Farner
            Assignee: Bill Farner


{{SchedulingFilterImpl}} has this snippet of code:

{code}
            Supplier<Collection<IScheduledTask>> activeTasksSupplier =
                Suppliers.memoize(new Supplier<Collection<IScheduledTask>>() {
                  @Override public Collection<IScheduledTask> get() {
                    return storeProvider.getTaskStore().fetchTasks(
                        Query.jobScoped(Tasks.INFO_TO_JOB_KEY.apply(task))
                            .byStatus(ACTIVE_NOT_PENDING_STATES));
                  }
                });
{code}

This results in a job-scoped query for every offer being compared to a task.  Since this operation
is already in the scope of a write lock, we could precompute this information from outside
the loop over offers and do the expensive query only once.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message