Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B buck
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 201
    • Issues 201
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • 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
  • Meta
  • buck
  • Issues
  • #395
Closed
Open
Issue created Aug 13, 2015 by Administrator@rootContributor

Slow build-steps: ~2-5s per module on cache hit

Created by: bkase

Thanks again, @dreiss for helping with my last issue.

The build is fast now, but there seems to a constant ~18sec overhead whenever buck build app is executed.

I attached traces, but it seems like there isn't much information on cache hit. Let me know if there is some way to produce more verbose profiling information.

clean build trace no-op trace

The gen-rule to hack in kotlin takes almost no time, but the cache hit for the module seems way too long.

I don't quite understand how the [cache] field in .buckconfig is supposed to affect performance, but changing mode to dir under [cache] doesn't seem to noticeably affect build times.

Our build time has already halved, but it would be really nice to shave off another 20s.

Thanks!

Assignee
Assign to
Time tracking