[GitHub] [beam] TheNeuralBit commented on issue #21474: Flaky tests: Gradle build daemon disappeared unexpectedly

[GitBox <gi...@apache.org>]

TheNeuralBit commented on issue #21474:
URL: https://github.com/apache/beam/issues/21474#issuecomment-1176790456

   Assigning to @kennknowles since you had the most recent comment in BEAM-13810:
   
   > The claim by the scan at https://ci-beam.apache.org/view/PostCommit/job/beam_PreCommit_Java_Cron/5164/ / https://scans.gradle.com/s/kcy27wmdenr6i/timeline?anchor=nuv4fm6q4n3ks is "2749 tasks executed in 128 projects in 12m 50.990s, with 480 avoided tasks saving 8h 2m 40.377s"
   > 
   > The documentation claims "The reasoning is simple: improve build speed by reusing computations from previous builds. However, the benefits are dramatic: we typically measure build times reduced by 15-75% on subsequent builds. We recommend profiling your build by using --profile to get a sense of how much impact the Gradle Daemon can have for you." but the build I link above was a fresh daemon (https://scans.gradle.com/s/kcy27wmdenr6i/performance/daemon says "0 previous builds") and still had many cache hits.
   > 
   > So it would appear that our local cache may make the daemon's in-memory incremental building less important.
   
   I think the takeaway here is that we should be able to turn on `--no-daemon` without a performance penalty?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org