Opened 7 years ago

Closed 7 years ago

#2777 closed task (complete)

Resolver research: cache algorithm

Reported by: shane Owned by: UnAssigned
Priority: high Milestone: Sprint-20130319
Component: resolver Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket: resolver-ng
Estimated Difficulty: 8 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

This ticket represents the work need to figure out what a reasonable approach for our cache design.

This is in the resolver_research_and_design branch, as described in:

doc/design/resolver/03-cache-algorithm

Subtickets

Change History (6)

comment:1 Changed 7 years ago by jelte

  • Milestone changed from New Tasks to Sprint-20130305

comment:2 Changed 7 years ago by shane

  • Priority changed from medium to high

Raising priority. Would be good to get done on this sprint!

comment:3 Changed 7 years ago by shane

  • Estimated Difficulty changed from 0 to 8

comment:4 Changed 7 years ago by jinmei

I'm not sure what's the expected procedure to complete this task,
but I've dumped my current thoughts on this topic to the branch.
Some others may want to add their own ideas, but at the moment
I'll move the ticket to the review queue.

comment:5 Changed 7 years ago by jinmei

  • Owner set to UnAssigned
  • Status changed from new to reviewing

comment:6 Changed 7 years ago by jelte

  • Resolution set to complete
  • Status changed from reviewing to closed

I think this one can be closed now.

Note: See TracTickets for help on using tickets.