Hardware specs: AWS cloud, Amazon Linux, 15GB RAM, 500 Provisioned IOPS SSD , 8 cores
]# 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) 120116
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 200000
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) 120116
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
We are trying to run ACL tool on SSD drive, but facing too many read reqs queued after 118sec, please have a look below.
ERROR: too many read reqs queued
drive(s) can’t keep up - test stopped
After 118 sec:
read-reqs queued: 99985
What we are missing here, could you please someone help to resolve this.
i2.4xlarge with an hvm AMZ instance is also a good choice. But as always I would recommend benchmarking the system for your particular case before going live in production.
We do offer an ssd certification tool that can be used to validate your drives:
The Number of ram will deepen don the size of your data as index would need 64 bytes per records.
You can use following links for calculating storage space for your particular data: