0

I have recently set up JFrog Container Registry (v7.46.11) using its helm installer.

Some stats:

Docker images uploaded: ~ 30
Binaries Size: 42 GB
Binaries Count: 600
Artifacts Size: 105 GB
Artifacts count: 1200
File system: Used: 147 GB / 500 GB (29.4%)
No of concurrent users: 1 (that's right) and most of time it's idle. Essentially, no one is using it right now.

Issue is when I try logging in, the JFrog logo keeps showing up for almost 30-40 secs.

enter image description here

In all sincerity, I love the logo but not the duration for which it displays itself before actually showing the login screen. After logging in, everything works fine. No slowness is observed after that. To reduce the logo show time, I tried increasing the xms and xmx parameter along with the request and limits parameters as well but I don't see any change in the logo display duration. Is there any other JVM option that needs tweaking?

resources:
  requests:
    memory: "4Gi"
    cpu: "2"
  limits:
    memory: "5Gi"
    cpu: "4"
 ## The following Java options are passed to the java process running Artifactory.
 ## You should set them according to the resources set above.
 ## IMPORTANT: Make sure resources.limits.memory is at least 1G more than Xmx.
javaOpts:
  xms: "4g"
  xmx: "4g"
Technext
  • 7,887
  • 9
  • 48
  • 76
  • The log should be showing for so long. My immediate suspicion is that there are not enough resources. For the sake of experiment, can you double the container's memory and CPU allocated and see the impact? The UI is waiting for the Artifactory engine to be up and ready. A slow starting Artifactory is usually a sign of not enough resources. – Eldad Assis Dec 11 '22 at 11:05

0 Answers0