Bitswap Improvements Landed in js-ipfs?

[christroutner]

This issue is an extension of this discussion forum thread. In that thread, I document a high percentage (85%) of data received by a node is redundant, duplicate data.

This Issue in go-ipfs introduces improvements that reduce this duplicate data. It appears to have landed in the go-ipfs implementation.

Has this code landed in js-ipfs? If so, can someone provide a link to the commit? If not, are there any plans or open Issues about it? I might try to contribute to helping it land.

I'm running a fork of v0.55.4 of js-ipfs for my own project. If these bitswap improvements have landed in a new version, then I want to update and bring them into my project.

[welcome[bot]]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[welcome[bot]]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[christroutner]

Tagging @dirkmc as he's listed as lead maintainer of js-ipfs-bitswap.

[AnthonyAkentiev]

@dirkmc @christroutner Any info regarding this issue?

[christroutner]

The topic of the improvements landing, I haven't gotten any updates.

I ended up my software stack from js-ipfs to go-ipfs, controlling an external node with ipfs-http-client. I was able to take advantage of all the latest optimizations that way.