...
Disk Group 1 | 8 x 300 GB in RAID5 configuration (Used for Oracle Data Tablespace) Format the stripe with a block size that is optimal for data throughput. (typically 4Kb) |
Disk Group 2 | 4 x 146 GB in RAID 1+0 configuration (Used for Oracle Redo) Format the mirror with a block size of 512 bytes. 2 redo groups multiplexed |
Disk Group 3 | 2 * 146 GB in RAID 1+0 configuration (Used for Oracle Undo) Format the mirror with 4Kb block size |
Linux: limit on open file descriptors
On linux a limit can be imposed on the number of open file descriptors a user can have. You can see the current limit by running the ulimit command:
| Code Block | ||
|---|---|---|
| ||
> ulimit -a |
...
core |
...
file size (blocks, -c) 0 |
...
data |
...
seg size (kbytes, -d) unlimited |
...
scheduling priority (-e) 0 |
...
file size (blocks, -f) unlimited |
...
pending signals (-i) 3889 |
...
max |
...
locked memory (kbytes, -l) 64 |
...
max |
...
memory size (kbytes, -m) unlimited |
...
open files (-n) 1024 |
...
pipe size (512 bytes, -p) 8 |
...
POSIX |
...
message queues (bytes, -q) 819200 |
...
real-time |
...
priority (-r) 0 |
...
stack size (kbytes, -s) 8192 |
...
cpu time (seconds, -t) unlimited |
...
max |
...
user processes (-u) 3889 |
...
virtual memory (kbytes, -v) unlimited |
...
file locks (-x) unlimited |
...
The limit is given by the setting open files, in the above example 1,024. This is a common default on linux.
Ensure that the user that will run tomcat has a limit of at least 50,000, or is unlimited. Although PhixFlow will generally open only a fraction of 50,000 file descriptors, it is best to ensure that this limit can never be hit since otherwise numerous low level errors can occur.