[bisq-network/bisq] Improve GRADLE build Performance (PR #5822)

[Chris Beams]

A bit more detail on why this change doesn't make a difference:

@shisheng-1 wrote:
> This project has more than 1000 source files. 

True, but the devil is in the details. Per the [feature's documentation](https://docs.gradle.org/current/userguide/performance.html#compiler_daemon):

> It’s unlikely to be useful for small projects, but you should definitely consider it if a single task is compiling close to a thousand or more source files together.

There are just over 3000 source files across all Bisq subprojects, but no one subproject has more than 1000:

```
$ for i in $(echo */src */build); do echo -n "$i: "; find $i -name '*.java' | wc -l; done | grep -v ': 0'; echo -n 'TOTAL: '; find */src */build -name '*.java' | wc -l;
apitest/src: 74
assets/src: 264
cli/src: 88
common/src: 106
core/src: 958
daemon/src: 20
desktop/src: 530
inventory/src: 3
monitor/src: 27
p2p/src: 166
pricenode/src: 61
relay/src: 2
seednode/src: 3
statsnode/src: 2
proto/build: 754
TOTAL: 3058
```

So no single `compileJava` task is compiling over 1000 files, and certainly not most of them, therefore the overhead of the compiler daemon doesn't pay off and indeed becomes slightly counterproductive to build times. 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/5822#issuecomment-966966143
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211112/982bc82d/attachment.htm>