{"type":"rich","version":"1.0","author_name":"npub15fmnxm546tg2sv0l7elusrvqsgezdzdg3m0flpml5fr2qf3f5slskxlq6h","author_url":"https://nostr.ae/npub15fmnxm546tg2sv0l7elusrvqsgezdzdg3m0flpml5fr2qf3f5slskxlq6h","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2012-02-01\n📝 Original message:Hi Gregory,\n\nI played with the database sync as well to get further speedups, but in the latest version I could only get about 1% extra from this. \n\nIn the Satoshi client there is a bunch of sleeps and mutexes (put in there with great generosity)  for making threads run smoother and to avoid deadlock I guess.\n\nThe big change in speed came from moving from the threading based setup to the async based setup, so I think these are the culprit. Further, as I also write somewhere in the wiki. I can measure that 50% of the time is consumed in verify, so there is not much left to optimize now. Actually, Berkeley DB does a quite decent job in caching reads so not even a cache should help.\n\nCheers,\n\nM\n\nOn 01/02/2012, at 15:59, Gregory Maxwell wrote:\n\n\u003e On Wed, Feb 1, 2012 at 9:18 AM, Michael Grønager \u003cgronager at ceptacle.com\u003e wrote:\n\u003e\u003e The libcoin/bitcoind client downloads the entire block chain 3.5 times faster than the bitcoin/bitcoind client. This is less than 90 minutes on a modern laptop!\n\u003e \n\u003e Very interesting. Do you know where this speedup came from?  It's not\n\u003e typical for straight refactors that don't change datastructures and\n\u003e the like to see such big speedups.\n\u003e \n\u003e I see you have commented out code that disables fsync, which was my\n\u003e first guess since I get big speedups from doing similar things.\n\nMichael Gronager, PhD\nDirector, Ceptacle\nJens Juels Gade 33\n2100 Copenhagen E\nMobile: +45 31 45 14 01\nE-mail: gronager at ceptacle.com\nWeb: http://www.ceptacle.com/"}