Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

largely populated AT instance running slow after v0.4 upgrade #1758

Closed
simondate opened this issue Oct 27, 2017 · 4 comments
Closed

largely populated AT instance running slow after v0.4 upgrade #1758

simondate opened this issue Oct 27, 2017 · 4 comments
Assignees
Labels
D: hard Complex issues, require discussion and big time commitment I: critical High impact bugs, breaking functionality for the end-user - should be fixed ASAP S: merged Completed, reviewed, and merged issues T: bug

Comments

@simondate
Copy link
Member

simondate commented Oct 27, 2017

Since we upgraded to v0.4 the AT has been running really slow (like takes 15s to load a course when it would previously take 2s).

This was never an issue on my local installation or our dev installation, which runs of the same server and config as the live one.

Versions

  • Authoring Tool Version: 0.4
  • Framework Version: 2.2.2
  • Operating System: Unix based server
  • Node version: 6.6.0
@simondate simondate changed the title largely populated AT instance running slow after 0.4 upgrade largely populated AT instance running slow after v0.4 upgrade Oct 27, 2017
@simondate
Copy link
Member Author

We've been looking at the developer tools network and it seems that when you navigate into a course from the dashboard lots of other courses seem to get loaded too.

@louisebennett
Copy link

@louisebennett
Copy link

I did some further testing into this:

On the Dashboard page, it first loads the json for each component/extension that is installed, and then each course in the (I assume) tenant. It also looks like a number of js files are being loaded in, including things like editors and plugin managers that (I'm guessing) shouldn't be there.

When you're editing an individual course, it loads in the components and extensions again, and then config for individual components, articles and pages.

Needless to say, the more courses you have in your tenant, the longer the load times are (the screenshot above was taken while the page was still loading).

@canstudios-louisem canstudios-louisem added this to the 0.4.1 Bugfixes milestone Oct 30, 2017
@taylortom taylortom self-assigned this Oct 31, 2017
@canstudios-louisem canstudios-louisem self-assigned this Nov 2, 2017
@canstudios-louisem canstudios-louisem added D: hard Complex issues, require discussion and big time commitment I: critical High impact bugs, breaking functionality for the end-user - should be fixed ASAP S: in-progress Issues currently being worked on - leave these be! T: bug labels Nov 2, 2017
@canstudios-louisem canstudios-louisem removed their assignment Nov 7, 2017
@simondate
Copy link
Member Author

@taylortom @canstudios-louisem is there anything we can do to help with this? We really want to be able to use the features of 0.4 but it's not in a workable state atm.

@canstudios-louisem canstudios-louisem added S: merged Completed, reviewed, and merged issues and removed S: in-progress Issues currently being worked on - leave these be! labels Dec 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
D: hard Complex issues, require discussion and big time commitment I: critical High impact bugs, breaking functionality for the end-user - should be fixed ASAP S: merged Completed, reviewed, and merged issues T: bug
Projects
None yet
Development

No branches or pull requests

4 participants