Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • N Nebulo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PublicAndroidApps
  • Nebulo
  • Issues
  • #260
Closed
Open
Issue created Sep 02, 2020 by Daniel Wolf@dwolfMaintainer

Weight first request less for dns speed test

The first request should be weighted less. In it no sessions are established yet and it has to be cold-started. This does not reflect how Nebulo normally runs, where it does have sessions and such.

The weighted response time shouldn't be used as min value for the best case measurement though.

Another option would be the ignore the first request entirely for the statistic, always firing n+1 requests. This wouldn't force me to chose some arbitrary weight.

Assignee
Assign to
Time tracking