Christopher Berner
Christopher Berner
Thanks for the additional info. I'm waiting for my bitcoin node to sync and will test locally. 2.1.4 changed the page caching algorithm to LRU, which is the most likely...
@raphjaph I have a fully sync'ed bitcoin v28.0.0 node running locally now with `bitcoind -txindex`. But ord fails with this error: ``` cargo run --release -- --data-dir=./ord_db-2-1-4 --index-cache-size 2147483648 --height-limit=400000...
@gmart7t2 what's the exact ord command you ran? I just ran this: ``` time cargo run --release -- --data-dir=./ord_db-2-1-4 --index-cache-size 2147483648 --height-limit=450000 index update Finished `release` profile [optimized] target(s) in...
I figured out the issue. There is a bug in 2.1.4 where the read cache is LRU, but the write cache became random eviction. I retested just now with: `cargo...
@raphjaph this is fixed in 2.2.0
Nope. I have stopped maintaining the MacOS support
Can you tell me a bit more about what your high level goal? It sounds like you're trying to improve `read()` throughput by adding multiple threads
Ya, this should be fixed. It looks like libfuse has special handling for this case: https://github.com/libfuse/libfuse/commit/055478f11dd4f3d46653f89ffe63f7c5a400b114
Can you tell me more about the use case? I'm trying to understand if this is common enough that it should be support in fuser
I see, thanks for the links! It sounds to me like the best thing to do is to add a method like `Session::from_raw_fd`. You can then open `/dev/fuse` and call...