istae
istae
it should observed in the testing sessions after the cleanup is done that this issue is gone
Attached is the cpu profile of bee 2 [pprof.bee.samples.cpu.071.pb.gz](https://github.com/ethersphere/bee/files/14126875/pprof.bee.samples.cpu.071.pb.gz) 
one clue is localstore size may affect things as well.
The localstore should ideally looks like this. The localstore exports core, parent functions like Reserve.Put. The parent func initiates a Transaction. Any internal storage calls the parent function makes must...
wrapSync should be removed with a multex in chunkstore ( see storer/reserve.go for what is a multex)
these peers have a radius != 9 and zero neighbors, notice their reachability [bad-peers.txt](https://github.com/ethersphere/bee/files/12477056/bad-peers.txt)
it's most likely improper setups like firewall and nat issues. The other being hardware limitations. A bee node has to maintain somewhere around 150 tcp connections open and these nodes...
it would be great to have some logs and metrics from when this sort of thing happens
@ldeffenb what we are thinking is the encryption header should be on by default so that the node encrypts the uploaded data. any download endpoint can then be used with...