Commit d77e6716 authored by Philip Carns's avatar Philip Carns
Browse files

disable mercury checksums in perf regressions

parent e198740d
......@@ -80,6 +80,6 @@ packages:
mochi-ssg:
variants: +mpi
mercury:
variants: ~boostsys
variants: ~boostsys ~checksum
libfabric:
variants: fabrics=psm2,sockets
......@@ -96,7 +96,7 @@ packages:
mvapich2@2.2: /soft/libraries/mpi/mvapich2/gcc/
buildable: False
mercury:
variants: ~boostsys
variants: ~boostsys ~checksum
libxml2:
paths:
libxml2@2.9.1: /usr/
......
......@@ -59,4 +59,4 @@ packages:
libfabric:
variants: fabrics=gni
mercury:
variants: +udreg ~boostsys
variants: +udreg ~boostsys ~checksum
......@@ -51,7 +51,7 @@ packages:
m4@1.4.17: /usr
buildable: False
mercury:
variants: ~boostsys
variants: ~boostsys ~checksum
openssl:
paths:
openssl@1.0.1f: /usr
......
......@@ -10,3 +10,6 @@ Notes:
* libfabric needs both `verbs` and `rxm` providers. If you configure with only `verbs`, you will get an error like this: `fi_getinfo() failed, rc: -61(No data available)`
* To run the server/provider in one process and client in another, you must disable 'cgroups': submit your job with `#BSUB -step_cgroup n`
* If you want the server/provider to run on one node and client on another, request multiple nodes with 'bsub' and run with 'jsrun -n 1 -r 1 -g ALL_GPUS'. You can background one jsrun to start the server and then run another jsrun to start the client
* Use argobots@main (at least until Argobots 1.1 is available) to avoid
potential performance problem with mutex lock implementation due to weak
atomic semantics
......@@ -45,7 +45,7 @@ packages:
mochi-ssg:
variants: +mpi
mercury:
variants: ~boostsys
variants: ~boostsys ~checksum
# the 'mlx' provider for libfabric is not maintained
# https://github.com/ofiwg/libfabric/issues/4806#issuecomment-461678426
libfabric:
......
......@@ -60,4 +60,4 @@ packages:
libfabric:
variants: fabrics=gni
mercury:
variants: +udreg ~boostsys
variants: +udreg ~boostsys ~checksum
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment