MultiChain Developer Q&A - Recent questions tagged blocksize

Creating transactions takes much longer, when I set the block-size to absolute minimum.

Thu, 31 May 2018 16:49:52 +0000

Hello!

I started some stress tests with various multichain configurations and found out that, if I set the block size to minimum, creating new transactions on one node takes much longer.

Here are my results with default multichain configuration:

Multichain Configuration (1st attempt):

target-block-time = 15
maximum-block-size = 8388608
anyone-can-connect = false
anyone-can-send = false
anyone-can-receive = false
mining-diversity = 0.3
mine-empty-rounds = 10
skip-pow-check = false
pow-minimum-bits = 8
max-std-tx-size = 4194304

Result with default configuration (1st attempt):

200 000 Transactions 50 minutes 32 seconds.

Result with changed multichain configuration (2nd attempt):

target-block-time = 2
maximum-block-size = 1024
anyone-can-connect = true
anyone-can-send = true
anyone-can-receive = true
mining-diversity = 0.0
mine-empty-rounds = 0
skip-pow-check = true
pow-minimum-bits = 1
max-std-tx-size = 1024

Result 2nd attempt:

200 000 Transactions 24 hours 15 minutes 20 seconds

Why creating transactions with this configuration takes much longer, than with the default configuration. I thought, when I set the block size and the transaction size to minimum, the blockchain would generate transactions much faster. It is also striking, that the hardware (RAM, CPU, HDD) workload was much higher, than the first attempt.

Could you please explain that to me, or send me a link?

I really appreciate any help you can provide.

Best regards,

Sandjar

Chain folder keeps growing

Wed, 30 Mar 2016 10:22:20 +0000

Hello,

I ran a test last night, in which I wanted to issue 30 000 assets from one node to another - nothing new, we done it many times. The only parameter we changed in params.dat file before we started this test is "mining-diversity", and set it to 0.75.

The setup was: three nodes on three servers "blockserver1", "blockserver4" and "blockserver5". The last one was connected to blockchain but stayed idle.

However, very strange thing happened. After our program finished inserting assets on server "blockserver1" onto address of node on "blockserver4", debug.log on "blockserver4" continued to write data (you can find most representative display in file "bs4-utst6-tail-debug-excerpt.png" of .zip archive I'll link later). We left it overnight, and when we came into the office this morning, folder "utest6" which was the name of the chain that we tested on was 58GB in size.

We left it for another 20ish minutes and checked it again. It grew to 59GB.

listassets command lists just 30 000 assets, our program is not working anymore (triple-checked it with additional top and ps -ef commands on all servers).

We wanted to know why this strange thing had happened. Also, I zipped some screenshots of our terminal (it would be insane if I zipped whole directory) with "du -h" and "tail -f debug.log" commands, and you can find it on following link: http://bit.ly/1MSdowd .

Also, if you have anything else you need, just send me a message, and I'll provide it to you.

Thanks in advance,
Sloba

What does blocksize mean specifically?

Thu, 10 Mar 2016 14:19:42 +0000

What does blocksize mean specifically?