Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • predi predi
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kjetil Thuen
  • predipredi
  • Issues
  • #50

Closed
Open
Created Jan 29, 2015 by Kjetil Thuen@kjetilMaintainer

Terrible performance in admin interface when activity log is of some size

When accessing predi over a slowish line, it seems the websocket times out several times when first logging in as an admin. It looks like this has to do with transfering the activity log (currently about 9000 entries). On a related note, opening the activities view is slow too, but this time around it is computing the page that takes some time.

I would expect the same to show up for users once there are several thousand trades in the log.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking