Not using default JVM memory limits setting Xms and Xmx to expected max range. (#4193)
* Adding GreenLightning
* fix missing quote
create object for json production
* turn off telemetry for default test
* allow any external domain or ip
* Update to next version and template construction
* Revert "Update to next version and template construction"
This reverts commit da4fbc3b085f6e3b3bb50283d4d6e79efffdd3bb.
* Revert "Revert "Update to next version and template construction""
This reverts commit eb05517a192554caec7c5f690eeaaab171a549b6.
* Revert "Update to next version and template construction"
This reverts commit da4fbc3b085f6e3b3bb50283d4d6e79efffdd3bb.
* fix host ip to 0.0.0.0 to take load
added database read tests
* response large enough for multi db
remove epoll, it was not helping
added required headers
* update list of which tests we have implmented
* removed unused dependency
* remove unrequired 16G memory grab to get past travis check.
* Update to next GL version to fix overload issue past 1.5M rps
Refine template method to remove dead argument
* simplify arg parse
fixed issue with multi db under heavy load
* updat to atomic int
* Removed support for MultiTest, not stable at this time.
* added clean for safety
* remove dead code
* remove old comments
* [ci fw-only Java/greenlightning]
added comment
* [ci fw-only Java/greenlightning]
Added tests for remaining multi, update and fortunes
* [ci fw-only Java/greenlightning]
disable update test, seems to be missing some writes.
* [ci fw-only Java/greenlightning]
re-test of DBUpdate
* [ci fw-only Java/greenlightning]
disabled multi and update while tracking issue
* fixed muti paylod response JSON dups.
* [ci fw-only Java/greenlightning]
narrow building
* [ci skip] update readme
* [ci fw-only Java/greenlightning]
Update to version supporting 0.0.0.0 wildcard host
* [ci fw-only Java/greenlightning]
explicit memory min/max setting instead of default
update to new maven for build
* lower required low end to 8G
* [ci fw-only Java/greenlightning]
dropped min to 6G