From a44d0e94726610b2247b5bac02706e1de7e6d105 Mon Sep 17 00:00:00 2001 From: Cedric Beust Date: Thu, 24 Dec 2015 21:02:00 +0400 Subject: [PATCH] Android timings. --- kobalt-incremental-tasks.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/kobalt-incremental-tasks.md b/kobalt-incremental-tasks.md index fee39a9a..25157d82 100644 --- a/kobalt-incremental-tasks.md +++ b/kobalt-incremental-tasks.md @@ -46,7 +46,7 @@ Another advantage of checksums is that they are generic and not necessarily tied Internally, Kobalt maintains information about all the checksums and tasks that it has seen in a file `.kobalt/build-info.json`. Whenever an incremental task is about to run, Kobalt compares its input and output checksums to the ones from the previous run and if any differs, that task is run. Otherwise, it's skipped. -Example timings: +Example timings for Kobalt: | Task | First run | Second run | | ---- | --------- | ---------- | @@ -58,6 +58,20 @@ Example timings: | kobalt:assemble | 42333 ms | 2130 ms | | | 70 seconds | 2 seconds | +Android (u2020): + +| Task | First run | Second run | +| ---- | --------- | ---------- | +| u2020:generateRInternalDebug | 33025 ms | 1652 ms | +| u2020:compileInternalDebug | 23 ms | 24 ms | +| u2020:retrolambdaInternalDebug | 234 ms | 255 ms | +| u2020:generateDexInternalDebug | 2 ms | 2 ms | +| u2020:signApkInternalDebug | 449 ms | 394 ms | +| u2020:assembleInternalDebug | 0 ms | 0 ms | +| | 33 seconds | 2 seconds | + + +