We have some optimization suggestions to use at your discretion. There are strategies to manage the disk space consumed by Nexus Repository Manager. You should note that downloading some search indexes, like Maven Central, can consume several GB of disk. This is highly installation specific.įor a detailed discussion of disk space, see this article. The bulk of disk space will be held by your deployed and proxied artifacts, as well as any search indexes. Sonatype Nexus, installed, consumes less than 100MB. If you do this you should increase RAM on the system accordingly. So factoring in operating system overhead you will need at least 4GB of RAM, assuming no other large applications are running on the machine.įor very large Nexus Repository Manager instances you will need to bump up the maximum heap space.
The default JRE max heap size of Nexus Professional is 768Mb, and the codebase of Nexus Repository Manager will consume approximately another 1GB. So any reasonably modern 2-4 core CPU will generally be sufficient for normal use. Nexus Repository Manager performance is primarily bounded by IO (disk and network) rather than CPU.
Oracle Java Cryptography Extension (JCE) Download CPU Installing it allows stronger encryption algorithms to be used. It is the user's responsibility to verify that installing JCE is permissible under local regulations. If you see : Illegal key size in your log is an indicator that Nexus requires the JCE.
Windows file paths should use forward slashes and not backslashes. The value is a file path to an executable, not a directory. # (modify this to absolute path if you need a Java that is not on the OS path)Ĭhange the value of the property to the absolute path to your new java executable.