What can Red Hat® Enterprise Linux® do? Find out in this chart of the supported and theoretical limits of the platform.
Supported limits reflect the current state of system testing by Red Hat and its partners for mainstream hardware. Systems exceeding these supported limits may be included in the Hardware Catalog after joint testing between Red Hat and its partners. If they exceed the supported limits posted here, entries in the Hardware Catalog will include a reference to the details of the system-specific limits and are fully supported. In addition to supported limits reflecting hardware capability, there may be additional limits under the Red Hat Enterprise Linux subscription terms.
Supported limits are subject to change as ongoing testing completes.
The following values are formatted as tested/supported [theoretical].
Maximum logical CPUs
Red Hat defines a logical CPU as any schedulable entity. So every core/thread in a multicore/thread processor is a logical CPU.
| Architecture |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| x86 |
16 |
32 |
32 |
32 |
N/A3 |
N/A3 |
| Itanium 2 |
8 |
256 [512] |
256 [1024] |
N/A3 |
N/A3 |
N/A3 |
| x86_64 |
8 |
64 [64] |
160 [255] |
448 [4096]13 |
768 [5120]14 |
768 [8192] |
| POWER |
8 |
64 [128] |
128 |
128 |
768 [2048]16 |
768 [2048] |
| System z |
64 (z900) |
64 (z10 EC) |
64 (z13) |
64 (z13) |
256 (z13) |
340 (z14) |
| ARM |
N/A |
N/A |
N/A |
N/A |
N/A |
256 |
Maximum memory
The architectural limits are based on the capabilities of the Red Hat Enterprise Linux kernel and the physical hardware. Red Hat Enterprise Linux 6 limit is based on 46-bit physical memory addressing. Red Hat Enterprise Linux 5 limit is based on 40-bit physical memory addressing. All system memory should be balanced across NUMA nodes in a NUMA-capable system.
| Architecture |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| x86 |
64GB1 |
64GB1 |
16GB2 |
16GB2 |
N/A3 |
N/A3 |
| Itanium 2 |
128GB |
2TB |
2TB |
N/A3 |
N/A3 |
N/A3 |
| x86_64 |
128GB |
256GB [1TB] |
1TB |
12TB [64TB]11 |
12TB [64TB]12 |
24TB [64TB] |
| POWER |
64GB |
128GB [1TB] |
512GB [1TB] |
2TB |
32TB17 |
32TB [128TB] |
| System z |
256GB (z900) |
1.5TB (z10 EC) |
4TB (z13) |
4TB (z13) |
10TB (z13) |
16TB (z14) |
| ARM |
N/A |
N/A |
N/A |
N/A |
N/A |
1.5TB [256TB] |
| Maximum x86 per-process virtual address space |
Approx. 4GB |
Approx. 4GB |
Approx. 3GB2 |
Approx. 3GB2 |
N/A3 |
N/A3 |
| Maximum x86_64 per-process virtual address space |
|
512GB |
2TB |
128TB |
128TB |
128TB |
| Maximum POWER per-process virtual address space |
|
|
|
|
|
4PB19 |
Minimum required memory
| Architecture |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| x86 |
256MB |
256MB |
512MB minimum, 1 GB per logical CPU recommended |
512MB minimum, 1 GB per logical CPU recommended |
N/A3 |
N/A3 |
| Itanium 2 |
512MB |
512MB |
512MB, 1 GB per logical CPU recommended |
N/A3 |
N/A3 |
N/A3 |
| x86_64 |
256MB |
256MB |
512MB minimum, 1 GB per logical CPU recommended |
1GB minimum, 1 GB per logical CPU recommended |
1GB minimum, 1 GB per logical CPU recommended18 |
1.5GB minimum, 1.5GB per logical CPU recommended18 |
| POWER |
512MB |
512MB |
1GB minimum, 2GB recommended |
2GB minimum, 2GB required per install |
2GB minimum, 2GB required per install |
2GB minimum, 2GB required per install |
| System z |
512MB |
512MB |
512MB |
512MB |
1GB |
1GB minimum, 2GB required for installation |
| ARM |
N/A |
N/A |
N/A |
N/A |
N/A |
2GB |
Minimum required disk space
| RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| 800MB |
800MB |
1GB minimum, 5GB recommended |
1GB minimum, 5GB recommended |
10GB minimum, 20GB recommended |
10GB minimum, 20GB recommended |
File systems and storage limits
Ext3
| Feature |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| Maximum file size |
2TB |
2TB |
2TB |
2TB |
2TB |
2TB |
| Maximum file system size |
2TB |
8TB |
16TB |
16TB |
16TB |
16TB |
| Maximum subdirectories |
32000 |
32000 |
32000 |
32000 |
32000 |
32000 |
| Maximum symlink depth |
8 |
8 |
8 |
8 |
8 |
8 |
| ACL support |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Ext4
| Feature |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| Maximum file size |
-- |
-- |
16TB |
16TB |
16TB |
16TB |
| Maximum file system size |
-- |
-- |
16TB [1EB] |
16TB [1EB] |
50TB [1EB] |
50TB [1EB] |
| Maximum subdirectories |
-- |
-- |
65000/unlimited |
65000/unlimited |
65000/unlimited |
65000/unlimited |
| Maximum symlink depth |
-- |
-- |
8 |
8 |
8 |
8 |
| ACL support |
-- |
-- |
Yes |
Yes |
Yes |
Yes |
GFS
| Feature |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| Maximum file size |
2TB |
16TB [8EB] |
16TB [8EB]4 |
N/A |
N/A |
N/A |
| Maximum file system size |
2TB |
16TB [8EB] |
16TB [8EB]4 |
N/A |
N/A |
N/A |
| Maximum subdirectories |
-- |
unlimited |
unlimited |
-- |
-- |
-- |
| Maximum symlink depth |
-- |
unlimited |
unlimited |
-- |
-- |
-- |
| ACL support |
-- |
Yes |
Yes |
-- |
-- |
-- |
GFS2
| Feature |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| Maximum file size |
-- |
-- |
100TB [8EB] |
100TB [8EB] |
100TB [8EB] |
100TB [8EB] |
| Maximum file system size |
-- |
-- |
100TB [8EB] |
100TB [8EB] |
100TB [8EB] |
100TB [8EB] |
| Maximum subdirectories |
-- |
-- |
-- |
unlimited |
unlimited |
unlimited |
| Maximum symlink depth |
-- |
-- |
-- |
unlimited |
unlimited |
unlimited |
| ACL support |
-- |
-- |
-- |
Yes |
Yes |
Yes |
XFS
| Feature |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| Maximum file size |
-- |
-- |
100TB [8EB] |
100TB [8EB] |
500TB [8EB] |
8EB |
| Maximum file system size |
-- |
-- |
100TB [16EB] |
300TB [16EB]15 |
500TB [16EB] |
1PB |
| Maximum subdirectories |
-- |
-- |
unlimited |
unlimited |
unlimited |
unlimited |
| Maximum symlink depth |
-- |
-- |
8 |
8 |
8 |
8 |
| ACL support |
N/A |
N/A |
Yes |
Yes |
Yes |
Yes |
Storage
| Feature |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| Maximum Boot LUN size (BIOS) |
-- |
-- |
2TB |
2TB7 |
2TB7 |
2TB |
| Maximum Boot LUN size (UEFI) |
-- |
-- |
N/A |
32bit (i686) - 2TB, 64bit - 16TB (tested limit) |
50TB |
8EB |
Maximum number of device paths (sd devices) |
256 |
256 9 |
1,024 9,10 |
8,192 9,10 |
10,000 9,10 |
10,000 9,10 |
Kernel and OS features
| Feature |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| Kernel foundation |
Linux 2.4.21 |
Linux 2.6.9 |
Linux 2.6.18 |
2.6.32 - 2.6.34 |
3.10 |
4.18 |
| Compiler/toolchain |
GCC 3.2 |
GCC 3.4 |
GCC 4.1 |
GCC 4.4 |
GCC 4.8.2 |
GCC 8.2.1 |
| Languages supported |
10 |
15 |
19 |
22 |
22 |
TBD |
| NIAP/CC certified |
Yes (3+) |
Yes (4+) |
Yes (4+) |
Yes (4+) |
Under Evaluation (4+) |
Under Discussion |
| Common Criteria certified KVM |
-- |
-- |
Evaluated |
Evaluated |
Under Evaluation |
-- |
| IPv6 |
-- |
-- |
Ready Logo Phase 2 |
Ready Logo Phase 2 |
Under Evaluation |
Under Discussion |
| FIPS certified |
-- |
-- |
Yes (7 modules) |
Yes (8 modules) |
Under Evaluation (9 modules) |
Under Discussion |
| Common Operating Environment (COE) compliant |
Yes |
Yes |
N/A |
N/A |
N/A |
Under Discussion |
| LSB-compliant |
Yes - 1.3 |
Yes - 3 |
Yes - 3.1 |
Yes - 4.0 |
Under Evaluation (4.1) |
Under Discussion |
| GB18030 |
No |
Yes |
Yes |
Yes |
Yes |
Yes |
Client environment
| Feature |
RHEL 3 |
RHEL 4 |
RHEL 5 |
RHEL 6 |
RHEL 7 |
RHEL 8 |
| Desktop GUI |
Gnome 2.2 |
Gnome 2.8 |
Gnome 2.16 |
Gnome 2.28 |
Gnome 3.8 |
Gnome 3.288 |
| Graphics |
XFree86 |
X.org |
X.org 7.1.1 |
X.org 7.4 |
X.org 7.7 |
Wayland 1.158 |
| OpenOffice |
v1.1 |
v1.1.2 |
v2.0.4 8 |
v3.2 8 |
LibreOffice v4.1.4 8 |
LibreOffice v6.0.6.18 |
| GNOME Evolution |
v1.4 |
v2.0 |
v2.8.0 |
v2.28 |
v3.8.5 |
v3.28.58 |
| Default browser |
Mozilla |
Firefox |
Firefox 1.5 8 |
Firefox 3.6 8 |
Firefox 24.5 8 |
Firefox 60.5.18 |
Notes
- The SMP kernel supports a maximum of 16GB of main memory. Systems with more than 16GB of main memory use the Hugemem kernel. In certain workload scenarios it may be advantageous to use the Hugemem kernel on systems with more than 12GB of main memory.
- The x86 Hugemem kernel is not provided in Red Hat Enterprise Linux 5 or newer releases.
- Red Hat Enterprise Linux 6 and newer releases do not include support for the Itanium 2 architecture. Red Hat Enterprise Linux 7 and newer releases do not include support for the 32-bit x86 architecture.
- If there are any 32-bit machines in the cluster, the maximum gfs file system size is 16TB. If all machines in the cluster are 64-bit, the maximum size is 8EB.
- Officially support 125 CPUs across the entire machine.
- Requires Intel EPT and AMD RVI technology support.
- UEFI and GPT support required for more that 2TB boot LUN support: https://access.redhat.com/kb/docs/DOC-16981.
- Userspace applications will be updated during the life of the release.
- Larger numbers are possible, depending on testing and support by the specific hardware vendor. Consult your hardware vendor to determine their limit, and confirm with your Red Hat support representative. In no case will Red Hat support a limit that exceeds the limit supported by the hardware vendor.
- It may be necessary to increase certain driver parameters to reach these limits. Consult with your Red Hat support representative.
- Red Hat Enterprise Linux 6.7 is required for support of 12TB of RAM. Red Hat Enterprise Linux 6.6 can support up to 6TB of RAM. Previous versions of Red Hat Enterprise Linux 6, starting with Red Hat Enterprise Linux 6.3, support up to 3TB of RAM. Versions of Red Hat Enterprise Linux prior to Red Hat Enterprise Linux 6.3 support up to 1TB of RAM.
- Red Hat Enterprise Linux 7.2 is required for support of 12TB of RAM. Red Hat Enterprise Linux 7.1 can support up to 6TB of RAM. Previous versions of Red Hat Enterprise Linux 7 (i.e. Red Hat Enterprise Linux 7.0) support up to 3TB of RAM.
- Red Hat Enterprise Linux 6.7 or newer is required for 448 CPU support. The previous maximum supported CPU count for earlier versions was 288 CPUs.
- Red Hat Enterprise Linux 7.3 with errata kernel 3.10.0-514.26.2.el7 or newer is required for 768 CPU support. Red Hat Enterprise Linux 7.2 with errata kernel 3.10.0-327.18.2.el7 or newer is required for 576 CPU support. Red Hat Enterprise Linux 7.2 or newer is required for 384 CPU support. The previous maximum supported CPU count for earlier versions was 288 CPUs. Also, for 7.2 or newer, please refer to the following Red Hat Knowledgebase article: Memory swap occurs while the pagecache is reclaimed.
- Red Hat Enterprise Linux 6.8 or newer is required for 300TB XFS filesystem support on RHEL 6.x. The previous maximum supported XFS filesystem size in RHEL 6.7 and earlier was 100TB.
- Red Hat Enterprise Linux 7.5 or newer, Red Hat Enterprise Linux 7.4 Extended Update Support (EUS) kernel version 3.10.0-693.25.2.el7 or newer, or Red Hat Enterprise Linux 7.3 Extended Update Support (EUS) kernel version 3.10.0-514.48.1.el7 or newer is required for 768 CPU support. The previous maximum supported CPU count for earlier update releases or EUS kernels of Red Hat Enterprise Linux 7 was 192 CPUs.
- Red Hat Enterprise Linux 7.5 or newer, Red Hat Enterprise Linux 7.4 Extended Update Support (EUS) kernel version 3.10.0-693.25.2.el7 or newer, or Red Hat Enterprise Linux 7.3 Extended Update Support (EUS) kernel version 3.10.0-514.48.1.el7 or newer is required for support of 32TB of RAM. Previous update releases or EUS kernels of Red Hat Enterprise Linux 7 could support up to 2TB of RAM.
- Network / PXE install requires at least 1.5 GB of RAM for the install procedure only.
- For processors supporting 52-bit virtual addressing.
35 Comments
Very helpful information.
Very well done, indeed!
Excellent and very useful information .
Thanks for your useful information.
May I ask what is this mean?
For example, why the limit has two part of number? first 240 and second [5120]?
can you help me to understand, what is the [5120] mean?
thanks..
Hello Justin,
The first number is the tested limit, which is the maximum quantity that Red Hat's engineering and technical support teams have verified as fully functional for a given parameter. Certified systems are expected to behave correctly up to that limit. The second number is the theoretical limit, the maximum value the kernel and userspace, if applicable, should be able to support based on the current source code.
Hi,
Currently i'm using 30 days trial subscription for RHEL 6.6.
Server configuration: 2 x Xeon 6 core processor (with threading), 32 GB RAM.
Server carried high amount of network traffic, but server not take more than 55% CPU load.
I found that some CPUs are more than 80% free only 3 CPUs are 95% used.
Is trial subscription limits CPU usages/utilization?
Thanks.
Hello Rashed,
RHEL 6.6 eval subscription has no such CPU usages limitation. I suppose you should check network or your applications relevant issue or If you want to test 100% all CPU utilization on RHEL 6.6 then you can run multiple session of dd command or some other commands to generate CPU dummy load. Before this you should also ensure that the server hardware is certified with RHEL 6.6. You can use the following URL for hardware certification check on RHEL 6.
https://hardware.redhat.com/RHEL6
Best Regards
Deepak
Hi Deepak,
Thanks for your replay.
We found an issue with IRQ settings, we have changed IRQ & RPS settings & now its ok.
Thanks.
-Rashed
Thanks for the useful information
Which is the maximum LUN and physical volume size for RHEL 6 64bit?
From the point of view of the operating system, every path to a LUN is a separate device. As a result, we specify the max. number of paths that are supported (for example, 8,192 in RHEL 6). The number of LUNs will depend on the number of paths to those LUNs.
For the purpose of specifying the max. physical volume size, we use the largest supported filesystem size (100TB for RHEL 6). Although it is possible for a physical volume to have multiple filesystems (or logical volumes) on it, and the theoretical max. volume size is much larger, this limit is based on the largest volume we are able to test.
Very helpful information.
It is worth noting that minimum required RAM for normal installation via Anaconda for RHEL7 is 1 GiB but if you select all packages this can be as big as 1.5 GiB.
This seems be failing with 1 GiB with @base on RHEL 7.3 via Anaconda. I think we should change this to be at least 1.5 GiB for the RAM requirement. The same kickstart file worked fine under RHEL 7.2 with the memory at 1 GiB.
Anaconda in RHEL 8.1 seems to have even more demands when installing EFI system via Kickstart. I had to bump the memory to 3GB in order for the installation to proceed, otherwise I saw the famous "Pane is dead" error.
Well done fellas.
Missing the ACL limit for each filesystem
very helpful indeed.
The first row X86 Maximum logical CPUs it is listed as N/A with a note 6 note 6 talks about memory? looks like it should be note 8 8. Officially support 125 CPUs across the entire machine. this note talks about CPUs I cannot find anything on the list that has note 8 listed for note information
Actually, that note is saying that the memory number is N/A because those versions do not have a 32-bit x86 or Itanium2 version.
we are purchased the intel i3/i5 7th processor Dell/HP desktop systems, So, Im trying to install Redhat 6.5/7.4 but is is showing un supported hardware and is not entering into installation mode. kindly suggest solution
Greetings,
All certified hardware is listed in the Red hat Hardware catalog: https://hardware.redhat.com/RHEL
Please search the catalog to locate the model of interest. If it's not listed, then it may not have been certified by your favorite vendor. You can also cross reference the RHEL certification with the vendor's support website.
HTH
Ron
Red Hat Enterprise Linux 7.5+ requires 1.5 GiB as minimum amount of RAM for HTTP, HTTPS, or FTP network installation as per: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-installation-planning-disk-space-memory-x86
I'm sorry if this is in the wrong section but I'm having trouble installing RHEL7.5 on an Intel i7-8750H (Hexa Core) processsor. Can someone please point me to a list that shows the supported processor listing?
It is very helpful. Thank you.
Comprehensive!
Very helpful in order to know the capability and limits of redhat os
:)
helpful and easy to ready/format.
Very helpful.
very useful information
Good Work guys, keep it up
Helpful!!! ... Thank's
Awesome! Happy to have found this.