Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • F flyspray2gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Kevin Morris
  • flyspray2gitlab
  • Issues
  • #27
Closed
Open
Created Apr 10, 2021 by Kevin Morris@kevrOwner

Add a --threads option

To increase performance, we can add multithreaded HTTP requests toward Gitlab. This will, however, increase traffic and may be unwanted.

Proposal: Add a --threads option which allows the user to set the number of HTTP requests to perform at any one time. Default this option to a value of 1, causing one thread to be used for all requests.

This way, the user can then choose exactly how much traffic they'd like to hog.

Note With --threads, the order of catching exceptions and recovering from them changes with a multithreaded flow, as we can no longer simply treat it sequentially. We will need to modify the way we deal with exceptions during command_import.

Edited Apr 10, 2021 by Kevin Morris
Assignee
Assign to
Time tracking