| Summary: | 32 bit server kernel very slow when using > 4 GB RAM | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Nicolas Pomarède <npomarede> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | tmb |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel-server-4.4.26-1.mga5 | CVE: | |
| Status comment: | |||
|
Description
Nicolas Pomarède
2016-10-28 17:36:25 CEST
No, we wont build 32bit server kernel with CONFIG_VMSPLIT_2G=y It comes with it's own sets of issues with zero real gain. With big hw / memory, there is only one supported option ... use 64 bit. Status:
NEW =>
RESOLVED I don't know what the issues are, but the gain is not zero, the gain is to get normal speed with your PC and don't suffer from IO slowness. As a repeatable test, it actually takes 2 min to copy /var/lib/rpm which only consist of 70 MB, while it should take just a few seconds. Just face the facts... any 64bit capable hw, especially with 4+ GB of ram should be running 64bit... That's the only platform that get any real optimizations... I'm not interested in optimization, else indeed I would run 64 bit version. I have some legacy binary only 32 bit applications that I want to run under mageia. Up to know they worked correctly when I had 4 GB, after going to 8 GB, performance is dropping hugely. Adding 4 GB of RAM doesn't seem such a huge change in HW spec, I didn't expect such problems. After looking for a fix, I see that the user here : http://flaterco.com/kb/PAE_slowdown.html confirmed performances were restored with no visible drawbacks. Just to know, what are the issues you mentionned if the 2/2 split is used ? If mageia ships a 32 bit kernel that handles more than 4 GB, then I guess it's meant to be used and to work ? Else if it's a know fact that > 4GB causes problem, maybe the 32 bit kernel server should be limited to 4 GB, so users will really know they should use 64 bit version of the kernel for more RAM ? Or just remove 32 bit server version and user will know they have 32 bit desktop version or need to go 64 bit for server version ? It will work on atleast up to 8GB depending on how the memory gets set up... And I can happily run a quad-core 32bit buildsystem here with 8GB RAM without slowdown.... so the "tripping point" is not at 4GB, it's more like around 8GB (depending on whats running on the system and how its memory map gets set up) But we wont punish people with real 32bit-only hw on the behalf of people having 64-bit hw but want it to under-perform using 32bit installs. For example VMSPLIT_2G on 32bit server kernels would waste 1GB of userspace RAM for people having 32bit system with 4GB RAM. and 64bit installs can run 32bit apps just fine. Not to mention not all 3rdparty drivers will play nice with anything but the 3/1 split. iirc also wine gets into trouble if not using 3/1 split. |