Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 504
    • Issues 504
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 52
    • Merge requests 52
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #57

Closed
Open
Created Aug 24, 2018 by Ghost User@ghost

Fixes as a result of profiling the HTTP code and control channel

There are the following issues pertaining to JSONFeed and Http parsers which per my profiling tests seems to be first candidates for fixing:

  • JSONFeed::postBuffer expensive because of making new allocations all the time
  • JSONFeed::popNextFromBuffer makes many buffer de-allocations
  • JSONFeed::innerJSONHandler should not transition if the state remains the same
  • HttpResponseParser body handler is inefficient as it reads characters one by one
  • Connection::doTransaction should not reinitialize the parser all the time as it triggers expensive reinitialization of the state machine
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking