MR_BASIC/SCALABLE Deprecated

[jdinan]

Replace MR_SCALABLE and MR_BASIC with the new thing.

[wrrobin]

Need to remove MR_SCALABLE and replace MR_BASIC with the new MR modes.

[wrrobin]

@davidozog I am thinking, do we really need to provide the MR modes as config flags to users? Or, should we just set them based on the provider in use. In such case, we dont really have to consider if some certain flags are supported on a certain provider? If you agree, then we might be able to tie in other flags as well, that we provide through FI hints or add as options for performance reasons (i.e., hard polling v/s use of remote counters). Thoughts?

[davidozog]

I think one reason behind providing the MR modes as config flags is that it's generally difficult to establish a "best" set of these flags for all use-cases with any particular provider. Some providers have optional MR mode bits right?

You raise a good point though - I don't think I've met a user that actually cares about the MR bits - they usually just want things to work on the provider of their choice with decent performance ;). And yeah, SOS could eventually supply all provider-specific flags/parameters, but we'd want to be careful to avoid any combinatorial explosion in how the flags/params are organized/chosen in the transport code. And even then, some flags perform better with some applications than others, so we don't want to be too prescriptive - and yes, I can imagine new hints/options might help with that.

Anyway, not sure where that leaves us... but that's my 2 cents!

[markbrown314]

MR_BASIC/SCALABLE was removed in version 1.4.5.