Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mainnet batch creation minimum depth requirement #58

Closed
istae opened this issue Sep 10, 2023 · 5 comments · Fixed by ethersphere/bee#4331
Closed

mainnet batch creation minimum depth requirement #58

istae opened this issue Sep 10, 2023 · 5 comments · Fixed by ethersphere/bee#4331
Assignees
Labels

Comments

@istae
Copy link
Member

istae commented Sep 10, 2023

In order to improve batch utilization, the node should have some minimum depth requirement.
with a batch depth of something like 17 or 18, the batch runs out very quickly and unproportionally without filling most of the buckets available.
increasing depth improves utilization percentage.

Task:

  1. investigate which minimum depth gives at least 50% utilization.
  2. introduce the change in bee API
@nikipapadatou
Copy link

Input from the research team: If we need a minimum 50% utilisation this is the following:
Depth 23 gives a theoretical 48% and 24 gives 60%

@istae istae assigned mrekucci and unassigned acha-bill Sep 21, 2023
@istae
Copy link
Member Author

istae commented Sep 21, 2023

it was agreed on 20/9/2023 that the minimum allowed batch depth in the API should be 24.

@tmm360
Copy link

tmm360 commented Sep 21, 2023

@istae does it mean that the minimum allocable space will be ~68.72 GB? If it's right, this looks more a bad workaround than a solution.
Have you already evaluated a solution like this? ethersphere/bee#4292 (comment)

@istae
Copy link
Member Author

istae commented Oct 12, 2023

with this new test ethersphere/bee#4398
it was revelated that depth 22 can consistently provide > 50% utilization

@istae istae reopened this Oct 12, 2023
@istae
Copy link
Member Author

istae commented Oct 12, 2023

considering worst case scenarios, 24 gives better utilization, so it will remain 24

@istae istae closed this as completed Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants