--- Day changed Sun May 22 2016 00:00 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 00:01 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 00:01 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Ping timeout: 240 seconds] 00:15 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 00:18 -!- MarcoFalke [d537b8be@gateway/web/cgi-irc/kiwiirc.com/ip.213.55.184.190] has joined #bitcoin-core-dev 00:18 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 252 seconds] 00:22 < kanzure> matsuo is asking for information about known minimum requirements, but i think he wants to be using a fork of segnet, so i'm not sure what to tell him. 00:36 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 00:39 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 250 seconds] 00:41 -!- G1lius [~stefangil@94.242.243.239] has joined #bitcoin-core-dev 00:46 < BlueMatt> jonasschnelli: thats not a seed....thats a single host 00:46 < BlueMatt> (which is on a residential connection) 00:46 < tErik_mc1> yesterday, while my windows computer had around "6 weeks" of data left to complete blkchn sync, something happen, which i'm not sure, suddenly the monitor was blank, but OS seems to be still running fine, i can see drive led indicator blinking, and i could here audio from it . 1st time something like this happened ! had to force shutdown the pc. then bitcoin-qt keep on showinh error "Error reading from database, …" 00:47 < BlueMatt> jonasschnelli: but, it generally is incredibly reliable :) 00:47 < tErik_mc1> so i ran : bitcoin-qt -reindex , but its still 27weeks of blkchn remains to be synced :( is it ever gonna finish ? 00:48 < MarcoFalke> It could take longer than the initial download right now. 00:51 < tErik_mc1> according to byte counters, bitcoin-qt.exe has used only 20MB download & 114MB upload data. 00:52 < sipa> your block chain index or chainstate is likely corrupted 00:52 < MarcoFalke> jup, reindex will try to read from the disk first 00:52 < sipa> ah, during reindex it will not download, just process what you already have first 00:53 < tErik_mc1> so i guess, most files are there until yesterday's position of 7 week, until then it will not download anymore, but after reaching 7week position it will start download+sync again. 00:54 < sipa> yes 00:55 < tErik_mc1> hi sipa :) 00:56 < tErik_mc1> i talked with you in openbazaar slack chan. 00:56 < sipa> that is very unlikely 00:57 < tErik_mc1> ah i see, sorry about that, theres another user using similar handle as your there. 00:59 < tErik_mc1> If i quit from bitcoin-qt.exe now, and restart computer to complete a system-update, then do you guys think i will have to start re-index from beginning again ? 01:00 < sipa> you can quit and start again, but don't pass -reindex again 01:00 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev 01:00 < sipa> if you pass -reindex again, it will start over 01:00 < sipa> if you don't, it will continue 01:02 < tErik_mc1> ah i see, THANKS for clarifying. i wish i had much powerful processor than what is it now (an i3 with 1 core 4 thread) . i guess, if bitcoin-qt is put into a SSD drive then it will be super fast, right ? 01:03 < sipa> no, but increasing its database cache size will help (start with -dbcache=2000 if you want to give it 2 GB) 01:04 < tErik_mc1> 2GB of RAM, dedicated for it ? 01:04 < sipa> yes 01:04 < tErik_mc1> :) awesome :) 01:04 < sipa> or whatever number 01:04 < tErik_mc1> i sure can assign 2GB, this computer is 6GB. 01:06 < tErik_mc1> i was about to get those disk-caching software loaded into this, after reboot. 01:06 < sipa> don't 01:06 < tErik_mc1> you are sub-conscious mind-reader, or we have a link. 01:15 < tErik_mc1> the bitcoin-core supports & uses DNSSEC based verified DNS resolution or simple DNS resolution, i'm using "Unbound" local dns resolver. 01:16 < sipa> it just uses that to find other nodes 01:17 < tErik_mc1> If a bitcoin-core node is using residential ip-address, but it has a dyn-dns address (which resolves into that ip-address), then bitcoin-qt can be given -dns commandline option to connect with it ? 01:17 < sipa> please read the documentation (run bitcoind -help) 01:17 < sipa> -dns has nothing to do with all that, and it's on by default 01:17 < petertodd> jonasschnelli: looks fine here; we've had some dns issues that have been hard to track down... 01:19 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 01:20 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 01:21 < jonasschnelli> petertodd: Yes. Works again! 01:22 < petertodd> jonasschnelli: odd, I didn't change anything... :) 01:24 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 01:34 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 01:37 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 250 seconds] 01:42 -!- jtimon [~quassel@neubau-gw.kalkbreite.net] has joined #bitcoin-core-dev 01:45 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection] 01:55 -!- fengling [~fengling@114.111.166.228] has joined #bitcoin-core-dev 02:00 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 02:03 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 252 seconds] 02:04 < GitHub138> [bitcoin] theuni opened pull request #8085: p2p: Begin encapsulation (master...net-refactor13) https://github.com/bitcoin/bitcoin/pull/8085 02:14 < GitHub111> [bitcoin] sipa opened pull request #8086: Use SipHash for node eviction (master...moresiphash) https://github.com/bitcoin/bitcoin/pull/8086 02:19 -!- kadoban [~mud@unaffiliated/kadoban] has quit [Ping timeout: 276 seconds] 02:25 -!- fengling [~fengling@114.111.166.228] has quit [Ping timeout: 240 seconds] 02:27 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 02:30 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 240 seconds] 02:46 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 02:49 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 260 seconds] 02:50 -!- fengling [~fengling@114.111.166.228] has joined #bitcoin-core-dev 02:51 < GitHub147> [bitcoin] lclc closed pull request #6844: [REST] Add send raw transaction (master...sendrawtransactionREST) https://github.com/bitcoin/bitcoin/pull/6844 02:56 -!- Ginnarr [~Ginnarr@unaffiliated/ginnarr] has joined #bitcoin-core-dev 02:59 -!- fengling [~fengling@114.111.166.228] has quit [Ping timeout: 240 seconds] 03:02 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-bswalsfllghstqqw] has joined #bitcoin-core-dev 03:14 -!- gevs [~greg@unaffiliated/gevs] has quit [Ping timeout: 260 seconds] 03:19 < tErik_mc1> I restarted pc for system-upd, started bitcoin-qt with -dbcache=2048 option, bitcoin-qt started to verify blockchain, then started to re-index, from position where it was before, where i exited from btc-qt. now ram usage is higher than previous but not 2GB, its using around 630MB, 602MB, 577MB, 1.15GB (Private Bytes, Working Set, Private WS, Virtual Size). 03:20 < sipa> 2 GB is just a maximum, and only the db cache 03:21 < tErik_mc1> And I/O total is fluctuating from 25 to 47 MB/sec. 03:21 < sipa> during reindex? that's good 03:22 < tErik_mc1> ya, before restart, during re-indexing, it was using i/o close to 89 MB/s. 03:23 < tErik_mc1> But i guess thats because i assigned "higher" i/o priority and "higher" app priority. 03:25 < tErik_mc1> s/app/process/ 03:25 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 03:26 -!- gevs [~greg@unaffiliated/gevs] has joined #bitcoin-core-dev 03:36 -!- tErik_mc1 [~tErik@unaffiliated/terik] has quit [Ping timeout: 250 seconds] 03:44 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 03:47 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 260 seconds] 03:50 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 04:13 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 04:16 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 276 seconds] 04:30 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 04:34 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 276 seconds] 04:37 -!- fengling [~fengling@114.111.166.228] has joined #bitcoin-core-dev 04:42 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 04:44 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 240 seconds] 04:45 -!- Ginnarr [~Ginnarr@unaffiliated/ginnarr] has quit [Quit: Textual IRC Client: www.textualapp.com] 05:02 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 05:04 -!- afk11 [~afk11@109.255.154.81] has joined #bitcoin-core-dev 05:05 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 240 seconds] 05:06 -!- tErik_mc [~tErik@unaffiliated/terik] has joined #bitcoin-core-dev 05:07 -!- afk11 [~afk11@109.255.154.81] has quit [Quit: ZNC 1.6.3 - http://znc.in] 05:08 -!- afk11 [~afk11@109.255.154.81] has joined #bitcoin-core-dev 05:09 -!- afk11 [~afk11@109.255.154.81] has quit [Client Quit] 05:09 < tErik_mc> bitcoin-qt.exe now using 2.3 GB, 2.15 GB, 2.12 GB, 2.46 GB (Private Bytes, Working Set, Private WS, Virtual Size) memory. my router restarted, after that i now see, I/O total rate has fallen to mere 2 to 5 MB/s :( 05:14 < tErik_mc> I have now re-set bitcoin-qt.exe process priority to "Normal" & i/o priority to "Normal" level, now its shifting in between 5.6 to 14 MB/s. 05:18 < tErik_mc> And, after i/o & process priority set into "High" level, now shifting inbetween 7 to 17 MB/s. 05:24 < tErik_mc> Sync is still "22 weeks behind" :( 05:30 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 05:32 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Ping timeout: 252 seconds] 05:33 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 276 seconds] 05:52 -!- afk11 [~afk11@edwardsnowden1.torservers.net] has joined #bitcoin-core-dev 05:52 -!- afk11 [~afk11@edwardsnowden1.torservers.net] has quit [Changing host] 05:52 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev 05:58 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 06:00 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 246 seconds] 06:06 -!- afk11 [~afk11@unaffiliated/afk11] has quit [K-Lined] 06:22 -!- frankenmint [~frankenmi@174-25-25-137.ptld.qwest.net] has joined #bitcoin-core-dev 06:23 -!- fengling [~fengling@114.111.166.228] has quit [Quit: WeeChat 1.4] 06:24 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 06:25 -!- afk11 [~afk11@109.255.154.81] has joined #bitcoin-core-dev 06:25 -!- afk11 [~afk11@109.255.154.81] has quit [Changing host] 06:25 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev 06:26 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Remote host closed the connection] 06:27 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 276 seconds] 06:50 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 06:51 -!- afk11 [~afk11@109.255.154.81] has joined #bitcoin-core-dev 06:51 -!- afk11 [~afk11@109.255.154.81] has quit [Changing host] 06:51 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev 06:53 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 260 seconds] 06:55 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Client Quit] 07:01 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #bitcoin-core-dev 07:03 < tErik_mc> Restarted bitcoin-qt with -dbcache=1792 and immediately set i/o priority to "High", then process priority to "High", now total i/o rate is in between 25 to 45 MB/sec during re-indexing (in average i would say 40 MB/s) :) (and before that, during block verifying stage, i have seen 170 MB/s often, though it started with 240MB/s, then average rate was around 120 MB/s). 07:07 < tErik_mc> I think few other windows-services create conflicts or purposefully keeps (i/o r/w rate) speed at lower level, i just closed various "Intel" related stuff (this mobo is Intel chipset based) carefully, and few other apps & services from computer manufacturer too. 07:09 < tErik_mc> … before starting with -dbcache=1792 . 07:10 < luke-jr> tErik_mc: you may be CPU bound 07:10 < luke-jr> earlier blocks have no transactions/signatures to verify 07:11 < tErik_mc> bitcoin-qt is using around 25% cpu . its a i3 1 core with 4 thread 3.3GHz cpu, with 6GB 1333MHz ddr3 ram. 07:12 < luke-jr> maybe IO is low because the cache is sufficient? 07:12 < tErik_mc> actually fluctuating in-between 16% — 25% cpu usage. 07:14 < tErik_mc> yes, this cpu has much much less cache, only L2 256 KB, no L1 , no L3 :( and this hard drive is also a sata-ii ide 2.5". 07:15 < luke-jr> I'm talking about dbcache 07:15 < luke-jr> IO is only likely to occur much when you are overflowing that 07:15 < luke-jr> although I'd think you'd be getting more CPU use if it's just using cache mroe 07:16 < tErik_mc> i can max assign 3GB to this bitcoin-qt process, have other servers on this as well. 07:16 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 07:16 < tErik_mc> but bitcoin-qt seems to exceed what i'm specifying ! 07:16 < wumpus> 1792 already makes flushes very rare 07:18 < tErik_mc> so lets say 2048+768= 2816 MB would be better than 1792 MB dbcache ? 07:19 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 260 seconds] 07:19 < wumpus> hardly 07:19 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 07:20 < wumpus> the next step up would be setting dbcache high enough to fit the entire utxo set, 6000 or so, but I doubt you're limited by the db i/o 07:20 < tErik_mc> what min ram would be better ? 07:20 < tErik_mc> *min dbcache ram 07:21 < luke-jr> tErik_mc: GUI or RPC? are you polling it often? 07:21 < tErik_mc> GUI 07:21 < luke-jr> maybe see if RPC does any better? 07:22 < wumpus> did you change -par setting? 07:23 < tErik_mc> my side block-chain download isn't completed yet :( pc crashed yesterday, so i'm doing re-indexing, i was at "6weeks behind", ow at 18weeks behind. 07:24 -!- afk11 [~afk11@46.166.188.218] has joined #bitcoin-core-dev 07:24 -!- afk11 [~afk11@46.166.188.218] has quit [Changing host] 07:24 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev 07:24 < luke-jr> I don't see how that is relevant to our suggestions 07:24 < tErik_mc> no other than, -dbcache param, i haven't specific anything else, i have not created bitcoin.conf either. 07:24 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Client Quit] 07:24 -!- afk11 [~afk11@46.166.188.218] has joined #bitcoin-core-dev 07:24 -!- afk11 [~afk11@46.166.188.218] has quit [Changing host] 07:24 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev 07:25 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Client Quit] 07:25 < tErik_mc> no other param was specified other than -dbcache param , i have not created bitcoin.conf either. 07:25 -!- afk11 [~afk11@46.166.188.218] has joined #bitcoin-core-dev 07:25 -!- afk11 [~afk11@46.166.188.218] has quit [Changing host] 07:25 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev 07:25 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Client Quit] 07:26 -!- afk11 [~afk11@46.166.188.218] has joined #bitcoin-core-dev 07:26 -!- afk11 [~afk11@46.166.188.218] has quit [Changing host] 07:26 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev 07:27 < tErik_mc> by RPC, are you indicating i should run the bitcoind.exe daemon ? 07:27 < luke-jr> yes, after shutting down qt 07:29 -!- afk11_ [~afk11@46.166.188.218] has joined #bitcoin-core-dev 07:29 < tErik_mc> i have assumed that, bitcoind requires passing bunch of params in commandline, as i dont have an example command, i was using bitcoin-qt.exe 07:29 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 07:30 < MarcoFalke> It should not require any params 07:30 < tErik_mc> so for running bitcoind, i would 1st need to create+set the bitcoin.conf, and then run bitcoind and then bitcoin-cli, right ? 07:30 < luke-jr> just run it like you run qt 07:31 -!- afk11_ [~afk11@46.166.188.218] has quit [Client Quit] 07:31 < tErik_mc> ah i see. thanks. 07:31 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Ping timeout: 244 seconds] 07:34 -!- afk11 [~afk11@46.166.188.218] has joined #bitcoin-core-dev 07:34 -!- afk11 [~afk11@46.166.188.218] has quit [Changing host] 07:34 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev 07:36 < tErik_mc> i have started bitcoind, but forgot to specify -dbcache :( should i press Ctrl+C in Cmd.exe shell window, to stop it ? 07:38 < wumpus> bitcoin-cli stop 07:41 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 07:41 < tErik_mc> how do i specify parms to view debug info of category "bench" "net" etc ? 07:42 < MarcoFalke> -debug=net or -debug=1 07:43 < tErik_mc> and i should specify dbcache=6000 <— my max ram, right ? 07:44 < tErik_mc> windows or bios showed max 5.8 usable, so i guess i will specify -dbcache=5888 07:44 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 276 seconds] 07:44 < wumpus> specifying your entire usable ram as dbcache is not a good idea, other programs will also need memory 07:46 < tErik_mc> ah i see, so once bitcoind start to occupy more rams, avail rams for other will get reduced, and bitcoind will not release to them ofcourse. 07:49 < tErik_mc> then i will try with 2816, sparable at this moment , on this computer . but i also understand now what you've suggested then, unless its close to 6GB, i will not see much improvement. 07:55 < tErik_mc> My other location has a 24GB computer, i guess, i can try bitcoind with sufficient dbcache there. 08:03 < MarcoFalke> dbcache=1000 or 2000 should be sufficient to have a really low miss-rate 08:04 -!- alpalp [~allen@unaffiliated/alpalp] has joined #bitcoin-core-dev 08:08 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 08:10 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 08:11 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 276 seconds] 08:16 -!- cryptapus [~cryptapus@jupiter.osmus.org] has joined #bitcoin-core-dev 08:16 -!- cryptapus [~cryptapus@jupiter.osmus.org] has quit [Changing host] 08:16 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 08:17 < tErik_mc> BitcoinD seems to work at slightly higher rate than bitcoin-qt, max 5 MB/s difference (i guess around 8% difference) . both are fast at block-verifying stage, when re-indexing stage "XX Weeks Behind" begins, then they are again same rate . and both slowed down after 10 or so minutes of re-indexing :( 08:17 -!- cryptapus_afk [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 260 seconds] 08:19 < tErik_mc> i have by mistake (again) started, bitcoind, but this time with -dbcache=5888 (i pressed enter, before i could change it to 2816), now, bitcoin-cli stop is not working anymore, showing error code: -28 , error message: Verifying blocks… 08:20 < tErik_mc> i guess when it reaches re-indexing stage, then bitcoin-cli stop will work. 08:21 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has quit [Quit: Leaving.] 08:21 < tErik_mc> And btw, i did specify -debug=1 but its not showing any debug info inside CMD shell window :( 08:22 < MarcoFalke> You can try bitcoind -? to read the help. There is a section "Debugging/Testing options"... 08:23 < tErik_mc> But after specifying dbcache=5888, it seems, bitcoind is very slow at finishing "blockchain-verifying" stage . but bitcoin-qt was able to finish that stage with only 1792 dbcache param, at much faster with less time ! 08:24 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Read error: Connection reset by peer] 08:24 < tErik_mc> finally it fiished "blockchain-verifying" stage, now its stopping :) 08:24 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 08:27 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 250 seconds] 08:30 < tErik_mc> i'm looking at https://en.bitcoin.it/wiki/Running_Bitcoin . so may be bitcoind.exe supports -debug=net -debug=alert parameters, instead of -debug=1 . trying again. 08:31 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 08:33 < tErik_mc> or could it be, that, because of the -debug=1 params was given to bitcoind.exe , it was using slowed debug DLLs, instead of faster DLLs, and so it slowed down much ? 08:34 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 08:36 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 08:36 < wumpus> enabling all debug logging makes bitcoind marginally slower 08:38 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 246 seconds] 08:43 < tErik_mc> i tried again, this time with " bitcoind.exe -dbcache=2816 " only, though it began at much slower (8 MB/s) i/o rate & less cpu % usage, but after few mins, it sometime even reached 220 MB/s i/o rate , but averaging at 40 MB/s , and cpu usage remaining steady at 25% level . so in this turn it seems, its similar as bitcoin-qt. 08:45 < tErik_mc> But bitcoin-qt, always remains very fast at "blkchain-verifying" stage, and then initially very fast in "re-indexing", but slowed down few mins later. 08:51 -!- challisto [~challisto@c-76-16-149-33.hsd1.il.comcast.net] has joined #bitcoin-core-dev 08:51 -!- challisto [~challisto@c-76-16-149-33.hsd1.il.comcast.net] has quit [Changing host] 08:51 -!- challisto [~challisto@unaffiliated/challisto] has joined #bitcoin-core-dev 09:02 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 09:02 < tErik_mc> Since cpu is most of the time close to 25%, and since this i3 uP has 1-core with 4-hardware-threads (4-sub-core) , i guess bitcoin-core is using only 1 thread. i think i should find out how many threads it really using or just pass a param to use 3 threads. 09:05 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 260 seconds] 09:06 < tErik_mc> i see, i think i now understand the "par" param, i think i need to pass -1, so that 1 core remains free. 09:12 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 09:21 -!- MarcoFalke [d537b8be@gateway/web/cgi-irc/kiwiirc.com/ip.213.55.184.190] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client] 09:23 < tErik_mc> it seems -par=-1 reduces performance :( i will try other settings different time. 09:24 < tErik_mc> THANKS to all of you : wumpus , luke-jr , MarcoFalke , for your kind help, i will head out for now, be back few hours later. 09:24 -!- MarcoFalke [3e0caa9c@gateway/web/cgi-irc/kiwiirc.com/ip.62.12.170.156] has joined #bitcoin-core-dev 09:27 -!- MarcoFalke [3e0caa9c@gateway/web/cgi-irc/kiwiirc.com/ip.62.12.170.156] has quit [Client Quit] 09:29 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 09:32 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 260 seconds] 09:36 < luke-jr> I would expect that, yes… 09:36 < sipa> [A 09:40 -!- MarcoFalke [3e0caa9c@gateway/web/cgi-irc/kiwiirc.com/ip.62.12.170.156] has joined #bitcoin-core-dev 09:45 -!- droark [~droark@c-24-22-36-12.hsd1.or.comcast.net] has joined #bitcoin-core-dev 09:46 -!- MarcoFalke [3e0caa9c@gateway/web/cgi-irc/kiwiirc.com/ip.62.12.170.156] has quit [] 09:49 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 09:50 -!- tErik_mc [~tErik@unaffiliated/terik] has quit [Ping timeout: 276 seconds] 09:55 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 09:58 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 260 seconds] 10:01 -!- jtimon [~quassel@neubau-gw.kalkbreite.net] has quit [Ping timeout: 260 seconds] 10:16 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 10:21 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 10:24 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 240 seconds] 10:30 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 10:42 -!- kadoban [~mud@unaffiliated/kadoban] has joined #bitcoin-core-dev 10:48 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 10:50 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 260 seconds] 11:14 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 11:17 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 260 seconds] 11:21 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 276 seconds] 11:34 -!- G1lius [~stefangil@94.242.243.239] has quit [Read error: Connection reset by peer] 11:40 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 11:42 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 250 seconds] 11:52 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Quit: .] 11:52 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 12:43 -!- Samdney [~Samdney@dyn-ant666999.hawo.ipv6.uni-erlangen.de] has joined #bitcoin-core-dev 12:46 -!- frankenmint [~frankenmi@174-25-25-137.ptld.qwest.net] has quit [Remote host closed the connection] 12:48 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 12:50 -!- frankenmint [~frankenmi@174-25-25-137.ptld.qwest.net] has joined #bitcoin-core-dev 13:16 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer] 13:17 -!- frankenmint [~frankenmi@174-25-25-137.ptld.qwest.net] has quit [Remote host closed the connection] 13:23 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 13:33 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has quit [Quit: WeeChat 0.4.3] 13:34 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has joined #bitcoin-core-dev 13:34 -!- alpalp [~allen@unaffiliated/alpalp] has quit [Ping timeout: 260 seconds] 13:40 -!- alpalp [~allen@unaffiliated/alpalp] has joined #bitcoin-core-dev 14:19 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 14:26 -!- alpalp [~allen@unaffiliated/alpalp] has quit [Ping timeout: 260 seconds] 14:30 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 240 seconds] 14:37 -!- Samdney [~Samdney@dyn-ant666999.hawo.ipv6.uni-erlangen.de] has left #bitcoin-core-dev ["Verlassend"] 14:38 -!- shesek [~shesek@bzq-84-110-111-86.red.bezeqint.net] has quit [Ping timeout: 276 seconds] 14:42 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 15:01 -!- alpalp [~allen@104-54-235-28.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev 15:01 -!- alpalp [~allen@104-54-235-28.lightspeed.austtx.sbcglobal.net] has quit [Changing host] 15:01 -!- alpalp [~allen@unaffiliated/alpalp] has joined #bitcoin-core-dev 15:12 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 272 seconds] 15:15 -!- raedah [~x@172.58.41.91] has joined #bitcoin-core-dev 15:23 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #bitcoin-core-dev 15:33 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev 15:45 -!- alpalp [~allen@unaffiliated/alpalp] has quit [Ping timeout: 252 seconds] 16:20 -!- sanada [~bitktn@36-2-119-80.chiba.ap.gmo-isp.jp] has quit [Read error: Connection reset by peer] 16:47 -!- alpalp [~allen@104-54-235-28.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev 16:47 -!- alpalp [~allen@104-54-235-28.lightspeed.austtx.sbcglobal.net] has quit [Changing host] 16:47 -!- alpalp [~allen@unaffiliated/alpalp] has joined #bitcoin-core-dev 17:07 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 17:22 -!- sanada [sanada@36-2-119-80.chiba.ap.gmo-isp.jp] has joined #bitcoin-core-dev 17:40 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 17:41 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 17:41 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 18:01 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-bswalsfllghstqqw] has quit [Quit: Connection closed for inactivity] 18:55 -!- challisto [~challisto@unaffiliated/challisto] has quit [Quit: Leaving] 18:56 -!- fengling [~fengling@58.135.95.134] has joined #bitcoin-core-dev 19:01 -!- xiangfu [~xiangfu@58.135.95.135] has joined #bitcoin-core-dev 19:14 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving] 19:16 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 19:17 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 19:19 -!- hsmiths [~hsmiths@cpe-76-174-26-91.socal.res.rr.com] has quit [Quit: END OF LINE] 19:21 -!- xiangfu [~xiangfu@58.135.95.135] has quit [Ping timeout: 276 seconds] 19:21 -!- hsmiths [~hsmiths@cpe-76-174-26-91.socal.res.rr.com] has joined #bitcoin-core-dev 19:35 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 246 seconds] 19:50 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 19:54 -!- alpalp [~allen@unaffiliated/alpalp] has quit [Ping timeout: 260 seconds] 19:56 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 276 seconds] 20:09 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 20:38 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 264 seconds] 20:41 -!- xiangfu [~xiangfu@58.135.95.135] has joined #bitcoin-core-dev 20:44 -!- zooko [~user@2601:281:8000:8387:2c1c:224b:cf98:264f] has joined #bitcoin-core-dev 21:00 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 21:01 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 21:17 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 21:18 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 21:26 -!- zooko [~user@2601:281:8000:8387:2c1c:224b:cf98:264f] has quit [Ping timeout: 260 seconds] 21:32 -!- fengling [~fengling@58.135.95.134] has quit [Ping timeout: 240 seconds] 21:33 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 21:34 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 21:45 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has quit [Quit: Leaving.] 22:00 -!- fengling [~fengling@58.135.95.134] has joined #bitcoin-core-dev 22:08 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 22:09 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 22:34 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev 22:34 < dcousens> does OpenBlockFile cache at all? 22:35 < dcousens> nvm, it doesn't (excepting file system specifics) 22:38 -!- fengling [~fengling@58.135.95.134] has quit [Read error: Connection reset by peer] 22:40 -!- fengling [~fengling@58.135.95.134] has joined #bitcoin-core-dev 23:00 -!- MarcoFalke [3e0caa9c@gateway/web/cgi-irc/kiwiirc.com/ip.62.12.170.156] has joined #bitcoin-core-dev 23:03 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 23:04 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 23:21 -!- frankenmint [~frankenmi@174-25-25-137.ptld.qwest.net] has joined #bitcoin-core-dev 23:31 -!- xiangfu [~xiangfu@58.135.95.135] has quit [Ping timeout: 240 seconds] 23:31 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-lmiipweumzpzsksl] has joined #bitcoin-core-dev 23:40 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Quit: Lost terminal] 23:46 -!- xiangfu [~xiangfu@58.135.95.135] has joined #bitcoin-core-dev