Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE!
Implemented ability to use not only Epoch feed, but also Sequence feed.
Epoch vs. Sequence Feed types: speed comparison
The performance of the two types of feeds, Epoch and Sequence, in Bee was tested under two conditions: using a local Bee node and a remote FDS Bee node. The same script was used to test both feed types to ensure consistent conditions. The script performed the following tasks:
Here's a comparison of the execution times:
Local Bee Node Test:
Remote FDS Bee Node Test (https://bee-1.fairdatasociety.org/):
The Sequence feed took 18.9% longer than the Epoch feed when tested on the local Bee node. However, when tested on the remote FDS Bee node, the Sequence feed executed in just 50.2% of the time it took the Epoch feed, achieving a 49.8% improvement in execution time.
Despite the speed increase, it's worth clarifying with the Bee team about the possibility of parallel data uploading in Sequential feed for use in FairOS. If they've fixed this, it will work not only in fdp-storage but also in FairOS.