Skip to content

Change merging of ProtoViews to be O(N) instead of O(N*DEPTH) #3150

New issue
New issue
Closed
Closed
Change merging of ProtoViews to be O(N) instead of O(N*DEPTH)#3150
Assignees
tbosch
Labels
area: performanceIssues related to performanceeffort1: hours
Milestone
alpha-33

Description

@tbosch
tbosch
opened on Jul 20, 2015

The way we are merging proto views right now is an algorithm that merges bottom up for every components. This makes the overall runtime O(N*DEPTH) per component.

Activity

  1. tbosch
    self-assigned this
    on Jul 20, 2015
  2. tbosch
    added this to the alpha-33 milestone on Jul 20, 2015
  3. tbosch
    added
    comp: core
    area: performanceIssues related to performance
    P1: urgent
    effort1: hours
    on Jul 20, 2015
  4. tbosch
    closed this as completedin 078475aon Jul 21, 2015

  5. angular-automatic-lock-bot commented on Sep 6, 2019

    @angular-automatic-lock-bot
    angular-automatic-lock-botBot
    on Sep 6, 2019

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  6. angular-automatic-lock-bot
    locked and limited conversation to collaborators on Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: performanceIssues related to performanceeffort1: hours

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions