Skip to content

GitLab Next

    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Menu
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • G gitlab-pages
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 159
    • Issues 159
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-pages
  • Issues
  • #252
Closed
Open
Created Sep 20, 2019 by Nick Thomas@nick.thomas🆓Contributor

Domain scanning time reduced significantly

@krasio noted that the time taken to scan our pages configuration for gitlab.io reduced significantly on the 19th September: https://log.gitlab.net/goto/a87e3399d7ff8f5aac42b0a2cfde7e67

Screenshot_from_2019-09-20_10-28-13

Why this has happened is not certain. Perhaps it's an unalloyed good thing caused by the upgrade of a dependency (godirwalk for instance), in which case this issue can just be closed.

Another possibility is that configuration scanning time is affected by uptime - the longer a pages process is up, the longer the scan takes, perhaps? If that's the case, it's likely to be a resource leak of some sort and we should investigate.

First step: check back in a week. If scanning is taking significantly more than 5 minutes, that lends weight to theory 2.

Number of domains in the scan has not changed significantly.

Edited Sep 20, 2019 by Nick Thomas
Assignee
Assign to
Time tracking