@7th chapter of the Java Performance (by Charlie Hunt,..)
-XX:+DisableExplicitGC and runtime results of disabling explicit garbage collection is explained.
The following link is a reference for every java developer to learn more VM options. (I think the Java Performance also should be read.)
http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html
Wednesday, August 6, 2014
Should configuration filenames be hardcoded?
Please imagine one standalone application which uses some xml configuration files, reads them at the startup time & runs own business rules etc.
When we want to create a new another instance for this app in the same OS
Scenario 1: If you declare file name as constant in the source code, Its imposible to run a new application with different configuration.
Scenario 2: If you declare config file name such as command line parameter or another way, It is possible to run a new application instance in the same OS.
Actually, Scenarios could be changed according to your purpose.
My note is never give configuration file names as constant/hard coded (whatsoever I think you understood me) in the source code.
When we want to create a new another instance for this app in the same OS
Scenario 1: If you declare file name as constant in the source code, Its imposible to run a new application with different configuration.
Scenario 2: If you declare config file name such as command line parameter or another way, It is possible to run a new application instance in the same OS.
Actually, Scenarios could be changed according to your purpose.
My note is never give configuration file names as constant/hard coded (whatsoever I think you understood me) in the source code.