René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"setup-java post action caching for v4 is slower than v3","articleBody":"**Description:**\r\nWhen switching from setup-java v3 to v4 the post run part is significantly slower.\r\n\r\n**Task version:**\r\nv4\r\n\r\n**Platform:**\r\n- [x] Ubuntu\r\n- [ ] macOS\r\n- [ ] Windows\r\n\r\n**Runner type:**\r\n- [x] Hosted\r\n- [ ] Self-hosted\r\n\r\n**Repro steps:**  \r\n\r\nSlow:\r\n```\r\njobs:\r\n  verify:\r\n    runs-on: ubuntu-22.04\r\n    steps:\r\n      - uses: actions/checkout@v4\r\n        with:\r\n          fetch-depth: 0\r\n      - uses: actions/setup-java@v4\r\n        with:\r\n          java-version: '11'\r\n          distribution: 'temurin'\r\n          cache: 'maven'\r\n      - name: run maven\r\n        run: |\r\n          mvn -B --settings .mvn/settings.xml verify\r\n        shell: bash\r\n\r\n```\r\n![image](https://github.com/actions/setup-java/assets/135227466/ff42f60a-3597-441a-890e-e8367c7d2330)\r\n\r\n---\r\nFast:\r\n```\r\njobs:\r\n  verify:\r\n    runs-on: ubuntu-22.04\r\n    steps:\r\n      - uses: actions/checkout@v4\r\n        with:\r\n          fetch-depth: 0\r\n      - uses: actions/setup-java@v3\r\n        with:\r\n          java-version: '11'\r\n          distribution: 'temurin'\r\n          cache: 'maven'\r\n      - name: run maven\r\n        run: |\r\n          mvn -B --settings .mvn/settings.xml verify\r\n        shell: bash\r\n``` \r\n![image](https://github.com/actions/setup-java/assets/135227466/9320c7ea-e63b-4e83-bc3b-e2a58c2f1aa1)\r\n\r\n\r\n**Expected behavior:**\r\nv4 should have the same speed as v3. \r\nBoth executions had no cache hits and the amount of data was approx 30MB.\r\n\r\n**Actual behavior:**\r\nv4 is in this case orders of magnitude slower than v3.\r\n\r\n**Additional information:**\r\n\r\nI have seen that actions setup-node https://github.com/actions/setup-node/issues/878\r\nand setup-ruby https://github.com/ruby/setup-ruby/issues/543 have had the same problem.\r\nIt seems that it had to do with the upgrade of the actions/cache version.\r\n\r\nI think their solution was to exit the process manually after caching is complete as otherwise the job simply hangs until some timeout.\r\n\r\nAfter looking at this repo for a very short time **my guess** is that perhaps somewhere \r\nhere -\u003e https://github.com/actions/setup-java/blob/9704b39bf258b59bc04b50fa2dd55e9ed76b47a8/src/cache.ts#L150\r\na ` process.exit(0)` could solve the problem (as I said, I'm only guessing based on the node and ruby solutions).\r\n","author":{"url":"https://github.com/htpaf","@type":"Person","name":"htpaf"},"datePublished":"2024-02-29T10:50:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/601/setup-java/issues/601"}