-
1. Re: Wildfly 9.0.0CR1 memory needs...
pmm May 28, 2015 1:31 AM (in response to tdanecito)Run a load test, figure out what your live set size is, multiply by four. Run the load test again and check if your gc latencies are OK.
-
2. Re: Wildfly 9.0.0CR1 memory needs...
tdanecito May 28, 2015 9:21 AM (in response to pmm)Sorry I tried to make the question clear. After installing Wildfly 9.0.0.CR1 WITHOUT ADDING ANY APPLICATIONS what is the memory that is needed for Wildfly itself? Whan Red Hat says it is lightweight I expect memory needs for Wildfly itself to be low to start with. So what is the memory needs then? Does not Red Hat know??
Thanks,
-Tony
-
3. Re: Wildfly 9.0.0CR1 memory needs...
ctomc May 28, 2015 10:41 AM (in response to tdanecito)about 7-12MB heap is used by empty wildfly instance.
-
4. Re: Wildfly 9.0.0CR1 memory needs...
tdanecito May 28, 2015 1:43 PM (in response to ctomc)Many thanks Tomaz! I passed that along to the middleware group.
Is there a GA release date for Wildfly 9.0 publicized anywhere? Seems like Red Hat is close to releasing it.
Regards,
-Tony
-
5. Re: Wildfly 9.0.0CR1 memory needs...
pmm May 29, 2015 2:42 AM (in response to tdanecito)tony anecito wrote:
Seems like Red Hat is close to releasing it.
It's my understanding that WildFly is not a Red Hat product and not supported by Red Hat. It's a community project and supported by the community. JBoss EAP is a Red Hat product and supported by Red Hat.
-
6. Re: Wildfly 9.0.0CR1 memory needs...
ctomc May 29, 2015 5:09 AM (in response to pmm)Philippe Marschall wrote:
tony anecito wrote:
Seems like Red Hat is close to releasing it.
It's my understanding that WildFly is not a Red Hat product and not supported by Red Hat. It's a community project and supported by the community. JBoss EAP is a Red Hat product and supported by Red Hat.
Indeed, WildFly is community driven.
About 9 Final. you should really follow our twitter stream https://twitter.com/WildFlyAS/status/603650064058310657
If everything goes according the plan, we will release CR2 today and relabel it as .Final next week if there are no issues found.