full_node chia.full_node.full_node: WARNING Block validation time.....

[Kerby247]

What happened?

There are a lot of such warnings in the log. I don't understand what needs to be done to avoid this warning.
full_node chia.full_node.full_node: WARNING Block validation time: 3.45 seconds, pre_validation time: 0.72 seconds, cost: 5300154151, percent full: 48.183% header_hash: 5e22c3149dd3d088586e37a7983
bff1f78ffaccaca610a85f4c12c1cd3069148 height: 1707464

Version

1.2.11
1.3.0
1.3.1

What platform are you using?

Windows

What ui mode are you using?

CLI

Relevant log output

2022-03-17T18:23:20.900 full_node chia.full_node.full_node: WARNING  Block validation time: 3.66 seconds, pre_validation time: 2.20 seconds, cost: 333977102, percent full: 3.036% header_hash: 1577672a13903ea9aa6771168138c
162837328b6cd0c7c864fed0f7db755082a height: 1707450
2022-03-17T18:24:05.666 full_node chia.full_node.full_node: WARNING  Block validation time: 7.02 seconds, pre_validation time: 1.34 seconds, cost: 4066727816, percent full: 36.97% header_hash: f4e71cb94641229c285d67ba52f5
14969856beec6e3256cbf286243d7fefcc93 height: 1707454
2022-03-17T18:25:30.213 full_node chia.full_node.full_node: WARNING  Block validation time: 5.28 seconds, pre_validation time: 1.03 seconds, cost: 5414323437, percent full: 49.221% header_hash: 8daa3138f239438d7bd02db12d7
a7872540cbebebd8149f433aee50b8820118b height: 1707458
2022-03-17T18:27:00.182 full_node chia.full_node.full_node: WARNING  Block validation time: 3.45 seconds, pre_validation time: 0.95 seconds, cost: 4504999592, percent full: 40.955% header_hash: c8106d30ecb8ff6d346c582e579
29212fb4686d0ca8688652f982c539b3a2d9f height: 1707461
2022-03-17T18:28:03.525 full_node chia.full_node.full_node: WARNING  Block validation time: 4.08 seconds, pre_validation time: 1.45 seconds, cost: 4119227570, percent full: 37.448% header_hash: 51da055d815cf538b8836befc3b
c49e5e80bafbf8ae1099ee3d879d23fdc1741 height: 1707462
2022-03-17T18:28:33.760 full_node chia.full_node.full_node: WARNING  Block validation time: 3.45 seconds, pre_validation time: 0.72 seconds, cost: 5300154151, percent full: 48.183% header_hash: 5e22c3149dd3d088586e37a7983
bff1f78ffaccaca610a85f4c12c1cd3069148 height: 1707464
2022-03-17T18:29:10.073 full_node chia.full_node.full_node: WARNING  Block validation time: 3.22 seconds, pre_validation time: 0.72 seconds, cost: 290748551, percent full: 2.643% header_hash: 0999ebc07e70319968756b696019a
7ac711dca04879e033b58d103710aa7e16f height: 1707468
2022-03-17T18:32:41.715 full_node chia.full_node.full_node: WARNING  Block validation time: 2.17 seconds, pre_validation time: 0.61 seconds, cost: 1363808636, percent full: 12.398% header_hash: a95f1f4f6a83e6696578a4416fc
899ba53c391cdfc79f403e45c398551e156fa height: 1707482
2022-03-17T18:33:23.653 full_node chia.full_node.full_node: WARNING  Block validation time: 5.33 seconds, pre_validation time: 1.36 seconds, cost: 4817069223, percent full: 43.792% header_hash: c72f0dda4fde95b0d59d6f7d205
f0ca89d0a1c2fd245dfaaea86ead96b0cc24d height: 1707485
2022-03-17T18:34:01.825 full_node chia.full_node.full_node: WARNING  Block validation time: 4.78 seconds, pre_validation time: 1.23 seconds, cost: 4857102654, percent full: 44.155% header_hash: 1615e07f60024992fb1b444a5c6
7cf3a0fac0a14eeeff975f55b6e720b0e9a01 height: 1707486

[maaggg]

Hi. I have had the same problem for some time.

[LoudSyncro]

Same behaviour at my machine for many versions of chia.
Did a "google" research, but couldnt find an answer / explanation how to improve or if this is not important.

Version
still 1.2.11

What platform are you using?
Windows 10

What ui mode are you using?
GUI

Specs:
AMD 3900X (12c/24t)
128GB ECC RAM
LSI SAS 9305-24i
~ 2400 K32 plots on ~ 23 HDDs via HBA internal (LSI SAS 9305-24i )
OS on fast SSD (lots of free disk space)
Pagefile on fast NVME

Connection to 60 other nodes established (80 - 90% fully synced)

No other heavy disk load apps are running (even PLEX has low volume; only private single use).

So a clear answer would nice if sth is wrong / misconfigured. Even though I know response times of below 5 sec are ok

[Kerby247]

Apparently there is no dependence on the iron used. In my case, this is the FX8350 and 16 Gb of RAM. The blockchain base is on an SSD plus 10 more forks are running on the same machine. And only 520 plots. I will assume that the matter is in connecting with the nodes, I can try to reduce the number of connections. Something like:
target_outbound_peer_count: 12
target_peer_count: 24
Or try other options like 4 and 12

[loppefaaret]

Sub 5 seconds block validation time is no problem - we introduced it with a lower threshold than needed - we are all seeing these of different rates.
if it starts getting over 5 seconds on a regular basis, you might want to start considering doing something about it
average block time is 9.375 seconds, so as long as you are below that cumulative, i dont see a big problem personally

[Wontell]

Im getting hundreds of these, this is 330TB machine, 10400F, 16GB RAM
The OS and database were installed to samsung evo 250gb SSD but after i noticed these errors i tried to solve it by cloning it to Samsung 850 PRO 1Tb SSD the one with MLC nand and still getting these, I dont have any old slow HDDs, i removed all of them, the system is just modern WD 14tb/16tb and Seagate exos 12tb to 18tb models
Its been 8 weeks since I won a block, even thou from what it says i should win one every 19-20 days, and before I was getting blocks properly with about 280TB, after I added more HDD im not winning anything, I even optimized all my plot files, run the plot test and deleted everything below 30 results and created new plots file while testing them and only keeping the good ones and all my plots are 30 or higher

2022-04-07T21:59:22.466 full_node chia.full_node.full_node: WARNING  Block validation time: 2.40 seconds, pre_validation time: 0.30 seconds, cost: 3610958478, percent full: 32.827% header_hash: 962f615d25859ef6e139d5d167db6c347d2306205adc010ea6b4ed24249bc1b2 height: 1805137
2022-04-07T22:00:03.931 full_node chia.full_node.full_node: WARNING  Block validation time: 2.11 seconds, pre_validation time: 0.31 seconds, cost: 4669686669, percent full: 42.452% header_hash: 9985df2693a74dddf45d4694516ec2a1239097eef18a35ba2d0921db9224b501 height: 1805138
2022-04-07T22:03:16.564 full_node chia.full_node.full_node: WARNING  Block validation time: 2.03 seconds, pre_validation time: 0.38 seconds, cost: 4100334492, percent full: 37.276% header_hash: 3d050b5f7259352a405bcab6e2d79939344d9ad6421ce3ec9917c8c9717effc1 height: 1805151

[loppefaaret]

First off, the listed WARNING from the log, is just about the node, and has no direct relation to being farming or anything else - it is purely how fast your node is to handle an incoming block.
as long as this is below 5 seconds in general, there is nothing to worry about. even the faster machines get these, as you can see based on your own hardware.
just as a sidenote, when you run chia plots check it runs a static challenge against the plot, and this does not change, unlike real block challenges, that changes every round - so you might score 30+ aginst this static challange issued by chia plots check, but that changes for each new challenge you get while farming... it is meant as a way to verify that a given plot does not return way under expected values.
if you issue 100 checks and it return 45, it is a good indication that the plotfile possibly hold invalid data... so having all you plots 30+ agains the static challenge, does not give you any better plots than all your plots averaging out at around the same, swinging from 0.7 - 1.3... but do not fear, that you got all 30+ against the static challenge does not neccesarrily mean that they are bad against other challenges - it is very random how good a plots proofs perform against a given challenge

[Wontell]

Thanks for replay.
What can solve this issue? Is this CPU dependent or media where the database is?
As far as what I did with the plots, i assume I didnt do worse then it was before?

[loppefaaret]

the node validation time, is a none issue, there is nothing you can do, other than upgrade the CPU - specifically cingle core perfomance - get a CPU with a higher single core perfomance - but it is far from needed - even the highest 12900k chips, will still see these messages on occasions.

As for your plots, no - you should not be any worse of now, it should be perfectly fine

[Kerby247]

Apparently, in the future, if this parameter increases, it will be necessary to use the GPU as in the MMX blockchain