Gld Development: Difference between revisions
Jump to navigation
Jump to search
(→TODO) |
No edit summary |
||
| Line 15: | Line 15: | ||
** Make sure the java memory can be configured individually per instance - on the command line. <tt>--memory 1024m</tt> that should override the value hardcoed in the wrapper. | ** Make sure the java memory can be configured individually per instance - on the command line. <tt>--memory 1024m</tt> that should override the value hardcoed in the wrapper. | ||
** Possibility to configure gc logging from command line <tt>--gc-logging /a/b/c-gc.log</tt>. | ** Possibility to configure gc logging from command line <tt>--gc-logging /a/b/c-gc.log</tt>. | ||
** Memory leak analysis. | |||
Revision as of 01:13, 7 September 2016
Internal
GitHub
TODO
- Outcome of JDG testing
- Make sure I can run two gld instances in parallel without interference. Currently there's just one log file ($(pwd)/gld.log) and this gets overwritten.
- Make sure the java memory can be configured individually per instance - on the command line. --memory 1024m that should override the value hardcoed in the wrapper.
- Possibility to configure gc logging from command line --gc-logging /a/b/c-gc.log.
- Memory leak analysis.