[
https://issues.apache.org/jira/browse/MRESOLVER-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842478#comment-17842478
]
Matt Nelson commented on MRESOLVER-554:
---------------------------------------
Disabling parallelPut was the immediate workaround.
With some testing it has been observed that 2-3 upload threads seems to be the
sweet spot on our artifact repository infra. But this causes the download
threads to now be constrained to the same parallelism as uploads.
For a ~90 module reactor deploying ~700 artifacts (jar, pom, site, javadoc,
source, etc...) these were the timings observed. When the infra is under
heavier load single threaded deploys have taken over 5 minutes for this reactor.
{noformat}
1 thread 210 seconds
2 threads 180 seconds
3 threads 113 seconds
5 threads frequent errors(5xx and timeouts)
{noformat}
> Support configuration of upload/download threads individually
> -------------------------------------------------------------
>
> Key: MRESOLVER-554
> URL: https://issues.apache.org/jira/browse/MRESOLVER-554
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Matt Nelson
> Priority: Major
>
> Parallel deploys were introduced in MRESOLVER-32. The thread pool
> configuration is shared for uploads and downloads. It has been observed in
> our environment that uploads frequently error out when attempting to upload
> with the default thread pool size(5), but conversely we don't see the same
> errors for downloads.
> The proposal is to support configuration of upload/download thread pools
> individually.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
