-Xnoclassgc By default the JVM unloads a class from memory when there are no live instances of that class left, but this can degrade performance. Turning off class garbage collection eliminates the overhead of loading and unloading the same class multiple times.
The concurrent collector is designed for applications that prefer shorter garbage collection pauses and that can afford to share processor resources with the garbage collector while the application is running. Typically applications which have a relatively large set of long-lived data (a large tenured generation), and run on machines with two or more processors tend to benefit from the use of this collector. However, this collector should be considered for any application with a low pause time requirement; for example, good results have been observed for interactive applications with tenured generations of a modest size on a single processor, especially if using incremental mode. The concurrent collector is enabled with the command line option -XX:+UseConcMarkSweepGC.
the options are based on what the OP found helpful and documentation hosted by oracle
I will agree that the cache size is excessive, but that defines the max size of the cache, allowing the jvm to use as much memory it needs for code without hitting the default limit
there is one "that looks helpful" that will be getting removed.
Given your complaint I will review all the options, I was planning on doing this anyway