Detail of the issue
System: Linux
Neuron version: 0.110.1
CKB node version: v0.110.0
CKB light node version: v0.2.4
Let me roast about the whole process: when I started Neuron for the first time, its update status was stillness. I thought that my Neuron was stuck, and then I restarted Neuron. It was still like this for 5 ~ 6 times. Then I came to Issue to find the answer. Fortunately, I discovered the same issue in Issue and learned to view Neuron's running logs and think about Neuron's synchronization mechanism. I found this synchronization mechanism very foolish.
1）Neuron defaults to setting the verification height, which can be found with Neuron/packages/Neuron wallet/. env/CKB_NODE_ASSUME_VALID_TARGET, but when the synchronization does not reach this height, there will be no prompt on Neuron's interface indicating that the background is updating the height, making users mistakenly think that Neuron is dead, causing them to repeatedly shut down Neuron and even suspect that their computer is malfunctioning。
2）You may say that you just need to open Neuron to stop caring about it, it will run on its own. Yes, but you're wrong, it will be affected by the head_ The memory exceeded 600Mb and died. Surprisingly, my machine has 16GB of memory and 8GB of swap area. I can't figure out why it died when it exceeded 600Mb and then stopped synchronizing myself. I paid the price of 3 days to wait for it。
3）I noticed a phenomenon when I was listening to the run.log and found that it had synchronized to the highest block (about 10 million blocks). My Neuron finally started the save synchronization block program, and I was happy to finally see the progress on Neuron's interface. However, happy times are always so short. After a period of time, the save synchronization block stopped, and a new round of synchronization started from scratch on the run.log, It is a long wait until the highest synchronized block is reached, and then continue to save the synchronized block. This is repeated in sequence, with a maximum of less than 1 million synchronized blocks saved each time. That means that to reach a maximum of 10 million blocks, I need to go through this wait for 10 times. I think I am crazy and I also need to worry about whether it will overflow memory and wait for nothing。well, Is this alternating preservation mechanism really effective and reasonable?
bundled-ckb.log
No response
main.log
No response
status.log
No response
Detail of the issue
System: Linux
Neuron version: 0.110.1
CKB node version: v0.110.0
CKB light node version: v0.2.4
Let me roast about the whole process: when I started Neuron for the first time, its update status was stillness. I thought that my Neuron was stuck, and then I restarted Neuron. It was still like this for 5 ~ 6 times. Then I came to Issue to find the answer. Fortunately, I discovered the same issue in Issue and learned to view Neuron's running logs and think about Neuron's synchronization mechanism. I found this synchronization mechanism very foolish.
1）Neuron defaults to setting the verification height, which can be found with Neuron/packages/Neuron wallet/. env/CKB_NODE_ASSUME_VALID_TARGET, but when the synchronization does not reach this height, there will be no prompt on Neuron's interface indicating that the background is updating the height, making users mistakenly think that Neuron is dead, causing them to repeatedly shut down Neuron and even suspect that their computer is malfunctioning。
2）You may say that you just need to open Neuron to stop caring about it, it will run on its own. Yes, but you're wrong, it will be affected by the head_ The memory exceeded 600Mb and died. Surprisingly, my machine has 16GB of memory and 8GB of swap area. I can't figure out why it died when it exceeded 600Mb and then stopped synchronizing myself. I paid the price of 3 days to wait for it。
3）I noticed a phenomenon when I was listening to the run.log and found that it had synchronized to the highest block (about 10 million blocks). My Neuron finally started the save synchronization block program, and I was happy to finally see the progress on Neuron's interface. However, happy times are always so short. After a period of time, the save synchronization block stopped, and a new round of synchronization started from scratch on the run.log, It is a long wait until the highest synchronized block is reached, and then continue to save the synchronized block. This is repeated in sequence, with a maximum of less than 1 million synchronized blocks saved each time. That means that to reach a maximum of 10 million blocks, I need to go through this wait for 10 times. I think I am crazy and I also need to worry about whether it will overflow memory and wait for nothing。well, Is this alternating preservation mechanism really effective and reasonable?
bundled-ckb.log
No response
main.log
No response
status.log
No response