Separate Max SimultaneousTransfers configuration for storage and retrieval deals

[jennijuju]

Checklist

• This is not a new feature or an enhancement to the Filecoin protocol. If it is, please open an FIP issue.
• This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
• I have a specific, actionable, and well motivated feature request to propose.

Lotus component

Other

What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

Currently, SimultaneousTransfers apply for all deals, storage providers can benefit from the separate configuration for storage and retrieval deals so they have more control over their service.

Describe the solution you'd like

Separate Max SimultaneousTransfers configuration for storage and retrieval deals

Describe alternatives you've considered

No response

Additional context

No response

[rjan90]

Storage Providers can get a lot of deals from one client (i.e Esturay) simultaneously, that can/will stay in a transferring state for a long time. If the Storage Provider then has a low/normal MaxSimultaneousTransfers=20, and the amount of storage-deals from that client are equal to this, another client (i.e web3.storage) could potentially be blocked from retrieving a file they have previously stored with the storage provider earlier.

Separating this into a configuration for both storage-deals and for retrieval-deals will allow the storage provider to always serve retrievals in a situation where they have a lot of storage-deals transferring.

[neondragon]

This makes sense to me. It increases flexibility and has no significant disadvantage that I can think of.

[jennijuju]

duplicated with #7030