[
https://issues.apache.org/jira/browse/AURORA-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Farner updated AURORA-1298:
--------------------------------
Assignee: (was: Bill Farner)
Since i'm going to be on vacation for a while, some notes in case anyone else
picks this up:
- Use benchmarks as the guide, toggling back and forth between the db and
in-mem task stores (note: acquaint yourself with selecting specific benchmarks
from comments in build.gradle)
- Specialized TaskStore API calls are likely to bear fruit, specifically
aggregations that are currently in code (AttributeAggregate, role/job summary)
- Add an API call to fetch a single ScheduledTask by String taskId early. I
took a stab at this, and it turned out the dynamic SQL required to handle
TaskQuery has a big performance hit (IIRC it was about 3x).
- Unscoped queries is likely to be a major issue requiring a revamp of
DbTaskStore.fetchTasks to support streaming results (myBatis does not support
this, so we need to use their RowBounds to manually paginate and feed an
Iterator).
> Make DbTaskStore performance suitable for use in production
> -----------------------------------------------------------
>
> Key: AURORA-1298
> URL: https://issues.apache.org/jira/browse/AURORA-1298
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Bill Farner
>
> The DbTaskStore implementation has so far only targeted behavioral compliance
> with InMemTaskStore. Use benchmarks to determine areas that require perf
> improvements and address them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
