hashmap
hashmap
Works as designed, what behavior would you expect in this case?
Mocking is fine in unit tests, the point of integration tests is to check how different components work together, not in isolation. You would end up testing your perfectly behaving...
I don't have a straight answer. Hyper has a lot of deps, mostly because it's built on top of tokio. At the same time it's pretty bare bones in terms...
I was skeptical about scalability requirements for grin node, but atm I'm not so sure anymore. I think it's already important to have a performant solution by default. I value...
@ignopeverell CPU load grows linearly with number of peers. Granted, IO may not be repsonsible for that, but `perf` shows that we spent most of the time calling `Thread::sleep` (see...
I don’t think the problem is nanosleep oer se, but the fact that we call it too often. We could increase timeouts, sacrificing some latency. The only way to remove...
I found it's croaring https://github.com/RoaringBitmap/CRoaring/blob/master/src/roaring_array.c#L767
Saw another report in gitter. I predict it may be a problem when we get enough nodes.
Memory-mapped file could help, unfortunately it's not yet supported by croaring (but supported by java and go versions) https://github.com/RoaringBitmap/CRoaring/issues/74
@Jimmy24651 sure, the workaround is in the issue text, `rm -rf ~/.grin/main/chain_data` (replace `main` with `floo` for floonet)