michael-o edited a comment on pull request #68: URL: https://github.com/apache/maven-resolver/pull/68#issuecomment-675873558
@dantran Thank you very much for testing. I assume that your project is not publically available. I will try to make some assumptions if you cannot share the trace logs: * What is the degree of parallelism you use? * Do your modules have a lot of dependencies? * Do you have many overlapping dependencies? There could be two explanations: * Many many dependencies cause a lot of requests to Redis. Rountrips add time. * Overlapping dependencies makes the entire build thread to wait. Consider the following example: You need 100 locks and one single artifact is already locked. You need to wait n seconds. Obviously the rest cannot continue. This is an issue I (guess) cannot solve. You properly nailed it: serialization. Do you think you could provide an obfuscated log? I'd like to see what is causing the delay. [Here](https://maven.apache.org/resolver-archives/resolver-LATEST/maven-resolver-synccontext-redisson/index.html) is the log config. One could consider to cache the Redisson locks globally, but I don't know whether this is a good idea at all. Nor do I want to make it any more complex than necessary. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
