Skip to content

Degraded performance after the migration to the new backend storage

Summary

After #6745 (closed) builds are 2-5 times slower than usual. I would expect an improved performance after such migration. We were warned about caches, ok, we but several builds later the situation is not much better.

Steps to reproduce

The "build" step usually finished between 2-5 minutes. Now it is around 8-11. Whole build was under 30 minutes, now it was 140 minutes. It seems the cause is file system - this takes few seconds locally:

22:52:25  [INFO] --- dependency:3.9.0:unpack-dependencies (unpack-jar-dependencies) @ glassfish-embedded-all ---
22:53:21  [1227.939s][info][gc] GC(371) Pause Young (Normal) (G1 Evacuation Pause) 2085M->692M(2500M) 28.382ms

https://ci.eclipse.org/glassfish/job/glassfish_build-and-test-using-jenkinsfile/view/change-requests/

https://ci.eclipse.org/glassfish/job/glassfish_build-and-test-using-jenkinsfile/job/PR-25756/

Priority

  • Urgent
  • High
  • Medium
  • Low

Severity

  • Blocker
  • Major
  • Normal
  • Low

Impact

We are just reexecuting jobs as none passed today - timeouts, incompatible JNA on the operating system (maybe another issue?), trustAnchors (workaround: delete maven cache and prevent staging repository downloads). Then we wait a long time ... change something and reexecute again. You can imagine how frustrating it is ... especially when locally everything works, builds do pass on GitHub Actions too and even on private Jenkins do.