<bitcoin-git>
[bitcoin] achow101 opened pull request #34603: wallet: Fix detection of symlinks on Windows (master...fix-listwallet-recursion-detect-symlinks) https://github.com/bitcoin/bitcoin/pull/34603
josie has quit [Server closed connection]
josie has joined #bitcoin-core-dev
warren_ has quit [Server closed connection]
warren has joined #bitcoin-core-dev
nickler_ has quit [Server closed connection]
nickler has joined #bitcoin-core-dev
Guest21 has joined #bitcoin-core-dev
Guest21 has quit [Client Quit]
memset has quit [Remote host closed the connection]
<andrewtoth>
During steady state with default dbcache, I find the node can run for several weeks before flushing due to memory.
<sipa>
andrewtoth: i'd expect it to matter significantly during IBD still?
<andrewtoth>
sipa: yes, since we don't have 31132
<sipa>
andrewtoth: the default is 450 MiB, surely higher numbers are faster, even with parallel fetch?
<andrewtoth>
l0rinc found with 31132 the gap is much smaller from default to max dbcache. So, bumping it a little would likely not have much effect (after 31132, today, yes it will help)
<andrewtoth>
sipa: Increasing dbcache a little bit will have probably a few less flushes in the whole IBD, and a little more uxto cut-through. Flushing is pretty well optimized though. The bottleneck is reading utxos one by one.
sliv3r__ has quit [Ping timeout: 265 seconds]
sliv3r__ has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
l0rinc_ has quit [Quit: l0rinc_]
oneeyedalien has joined #bitcoin-core-dev
Guest67 has joined #bitcoin-core-dev
Guest67 has quit [Client Quit]
w68 has joined #bitcoin-core-dev
w68 has quit [Client Quit]
oneeyedalien has quit [Quit: Leaving]
jerryf_ has joined #bitcoin-core-dev
jerryf has quit [Remote host closed the connection]
eugenesiegel has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] maflcko closed pull request #34593: fuzz: expand script verification flag testing to segwit v0 and tapscript (master...fuzz-script-flags-segwit-tapscript) https://github.com/bitcoin/bitcoin/pull/34593
jonatack has joined #bitcoin-core-dev
l0rinc has joined #bitcoin-core-dev
l0rinc has quit [Remote host closed the connection]
l0rinc has joined #bitcoin-core-dev
PaperSword has joined #bitcoin-core-dev
PaperSword has quit [Client Quit]
PaperSword1 has joined #bitcoin-core-dev
PaperSword1 is now known as PaperSword
<yancy>
darosior - Is your point that Sparrow can't do some of the things that the core wallet can do? No GUI does not mean no wallet.. Personally the only interaractions I've ever had with the core wallet are via the CLI.
PaperSword has quit [Quit: PaperSword]
PaperSword has joined #bitcoin-core-dev
jerryf_ has quit [Remote host closed the connection]
jerryf has joined #bitcoin-core-dev
jerryf has quit [Remote host closed the connection]
jerryf has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
bugs_ has quit [Quit: Leaving]
jackielove4u1 has joined #bitcoin-core-dev
jackielove4u has quit [Ping timeout: 245 seconds]
jackielove4u1 is now known as jackielove4u
eugenesiegel has quit [Ping timeout: 272 seconds]
jonatack has quit [Ping timeout: 265 seconds]
l0rinc has quit [Quit: l0rinc]
robszarka has quit [Read error: Connection reset by peer]
michaelfolkson has quit [Server closed connection]
michaelfolkson has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
memset_ has quit [Remote host closed the connection]
l0rinc has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 272 seconds]
jonatack has quit [Ping timeout: 272 seconds]
ghost43 has quit [Remote host closed the connection]
afiore has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
afiore has joined #bitcoin-core-dev
<l0rinc>
agree with andrewtoth, I rather think we might want to reduce the default dbcache slightly after #31132 lands to compensate for the extra threads. We already can't really run master on a 2 GB machine - though, to be fair, even compilation OOMs there without a swap...
<andrewtoth>
l0rinc: you mean we can't run with default configs on a 2 GB machine? We should be able to run master with memory constrained configs just fine.