Mirko Da Corte
Mirko Da Corte
I see, on POST /bzz API there is a parameter `swarm-deferred-upload` set default at true. Anyway, my test uploads are very very slow, I'm working with a local node connecting...
The node is running on a NAS, it doesn't have an SSD, but 4 HDD in raid5, and it wasn't at full charge. These are some logs from `iostat` during...
I will try to use SSD, but an upload speed of ~10kB/s is a no-sense, in any case. Clef have to scale on more cores, and this is a point...
@agazso I see, thank you for have pointed me at this issue. I will try to figure out a possibile solution. But in this case, how can nodes verify now...
Any news on this? Issue is still there. I'm using default configuration on disk space (BEE_CACHE_CAPACITY=1000000), it should be ~4GB, but this is my disk space graphic. ...
I've db nucked two of my nodes, let's see how it will evolve.
same, Thinkpad P15 Gen1
I don't agree. To explicit quote the token name remove any ambiguity. Important when some one is using bee for the first time. It's a very very simple implementation.
Will new version fix pinning inconsistencies, or it would be better to nuke db after storage refactoring is complete?
Please @istae reopen this and leave it open. Call must be async, if not now, at least in future. To close this is a bad decision, in my opinion.