227428c3a4
This is relevant mostly for the VMs. Allocating that much memory puts a lot of pressure on remaining pieces of the system as currently we allocate total of 12GB memory per VM instance in the CI pool. Default of 4GB hp should be enough to cover majority of the tests hence if there's any suite that requires more memory, setup.sh should be called there directly with an optimal value. This is done to make sure we can accomodate proper resources in the CI by knowing what are the actual requirements rather than just blindly allocating "as much as possible". Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ie958c518c7ed702b068c7fc9042183fdf41aa816 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> |
||
|---|---|---|
| .. | ||
| match_files | ||
| common.sh | ||
| iscsi.sh | ||
| nvmf.sh | ||
| pmem.sh | ||
| raid.sh | ||
| rbd.sh | ||
| spdkcli_job.py | ||
| tcp.sh | ||
| vhost.sh | ||
| virtio.sh | ||