[
https://issues.apache.org/jira/browse/PHOENIX-7842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078543#comment-18078543
]
Andrew Kyle Purtell commented on PHOENIX-7842:
----------------------------------------------
{{-T 1C}} ( or {{-T 4}} ) succeeds in speeding up the build by running the
shading in parallel.
||Variant||Wall time||Speedup||
|Sequential {{mvn -DskipTests clean package}}|26:37|1.0x|
|Parallel {{mvn -T 1C -DskipTests clean package}}|11:27|2.32x|
All four uberjars are byte-identical to the sequential build with the same
entry counts ( 91184 / 79276 / 40964 / 40966 ) and same byte sizes.
By also excluding {{phoenix-mapreduce-byo-shaded-hbase}} except from release
builds, the reactor drops from 16 → 15 modules and skips the ~3:41 of shading
work for that module. With parallel build enabled this doesn't change wall
clock much because {{phoenix-client-embedded}} dominates the shading phase, but
it removes that ~3:41 of CPU work and reduces aggregate build cost.
> Reduce the shading contribution to build time
> ---------------------------------------------
>
> Key: PHOENIX-7842
> URL: https://issues.apache.org/jira/browse/PHOENIX-7842
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Minor
>
> The Phoenix build takes ~25 minutes on a M4 macbook due to shading. With some
> simple changes for developer inner loop we can cut the time in half if not
> better.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
