RFR: 2340: CommitCommentsWorkItem executing in GitLab takes a lot of time [v3]

[Erik Joelsson]

On Mon, 12 Aug 2024 22:58:55 GMT, Zhao Song <zsong at openjdk.org> wrote:

>> Currently, if a user comments under a commit named "Merge" in GitLab, the CommitCommentsWorkItem will take about 8 hours to complete.
>> After investigation, I think there is a bug in GitLabRepository#getCommitTitleToCommitsMap
>> 
>> For GitLab repos, we need to build a hash map for mapping commit title to commits. The implementation of the map is Map<String, LinkedHashSet<Hash>>. We use LinkedHashSet here because we want the bot to check latest commits first.
>> 
>> If the map has already been built, then the bot will query new commits in the repo and adds the commits into the map. However, when adding the new commit hash to the map, the bot add it to the end of the LinkedHashSet. So new commits will be checked very late.
>> 
>> For commit titles like "Merge", sometimes, there can be around 50K commits in a repo. If the latest "Merge" commit is added to the tail of the LinkedHashSet, the bot must check all previous commits first, which takes a lot of time.
>
> Zhao Song has updated the pull request incrementally with one additional commit since the last revision:
> 
>   update

forge/src/main/java/org/openjdk/skara/forge/gitlab/GitLabRepository.java line 646:

> 644:             var hash = new Hash(commit.get("id").asString());
> 645:             var title = commit.get("title").asString();
> 646:             ((LinkedHashSet<Hash>) commitTitleToCommits.computeIfAbsent(title, t -> new LinkedHashSet<>())).addFirst(hash);

Instead of casting to LinkedHashSet, we can use the type directly in the type declaration for `commitTitleToCommits`. We can even use the new shiny `SequencedSet` interface to avoid specifying the concrete class.

-------------

PR Review Comment: https://git.openjdk.org/skara/pull/1682#discussion_r1715219258