WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Speed issues #72

@alexcouper

Description

@alexcouper

I want this tool to be slick and quick.

It's starting to look nice, but it's slow to load. There are ways we can make it quicker.

Break up the response

We could have the angular front end ask not for "all features" but instead "all features from this provider", followed by "all features from another" etc - so that the page appears in chunks. We'd still provide the option of asking for "all features" but just choose not to use it on our front end.

Pre fetch and store.

I think when it comes to viewing a feature and calculating differences between branches, we're going to need to be doing things more cleverly on the server.

One way would be to ask for more permission from the github user (for example) to auto set up a callback on commit hook. We can then recalculate every time we hear about a commit for a user, and the data will be sitting there when they hit the site.

We should also break up the feature view and have any planning info brought back separately to the source code stuff.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions