| Summary: | engine-setup: Change minimum memory requirement | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Andrew Cathrow <acathrow> |
| Component: | ovirt-engine-installer | Assignee: | Kiril Nesenko <knesenko> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | acathrow, dfediuck, iheim, juan.hernandez, mgoldboi, mzawdx, oschreib, rbalakri, ykaul |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | integration | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-13 19:32:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Andrew Cathrow
2012-02-19 02:11:45 UTC
Andrew/Doron: Any idea what's the right memory requirements for EAP6? there is a flag to workaround this check - is it good enough? (In reply to comment #2) > there is a flag to workaround this check - is it good enough? The question is if 4GB is still the right number - if we can reduce this to 3GB (for example) with EAP6 then that's better than forcing the user to override. In my experience I can run successfully the engine in machines with 2 GiB of RAM and assigning only 1 GiB of memory to the application server JVM. This of course is not the result of exahustive tests, but I think it is a good indication that 4 GiB it too conservative. As we will be running performance tests in the future I would suggest setting 2 GiB as an objective for small deployments. Then, if the performance tests give good results, we can reduce the requirements. I think we should be fine with allowing 2GB[1], and just showing a warning 4GB is recomended. we can tweak per feedback from community during testing if needed. (i hope the value is easy to change in some config) maybe the reports installer should block on say less than 3GB though. [1] iirc, we assume a system will have 2GB, minus some video memory or something like that. andrew - my comment 5 is actually current behavior - just showing a warning. are you looking to reduce the 2GB limit itself? (In reply to comment #6) > andrew - my comment 5 is actually current behavior - just showing a warning. > are you looking to reduce the 2GB limit itself? the 4gb is what I'm trying to reduce. to what? 3GB? 2GB minimum and recomended? I'm not sure 1GB as minimum is reasonable (mostly since we don't know). |