MultiChain Developer Q&A - Recent questions tagged scalability

Performance impact depending on the number of miners

Mon, 11 Feb 2019 12:34:11 +0000

Hi,

We are currently implementing a private blockchain that has initially 15 nodes as miners. If we increase the number of miners, would this have a significant impact on the a.) confirmation time of a transaction, b.) and the propagation time of committed blocks across the blockchain network.

I am new to the blockchain technology so I would like to understand how exactly the number of miners impacts the blockchain network.

Thank you!

IssueFrom and Publish performance as asset number grows

Tue, 10 Jul 2018 15:13:50 +0000

I've noticed the performance of both the IssueFrom and Publish calls degrade significantly as the number of assets on the chain grows, even at relatively small numbers.

I found that the first issue command took 4ms, but the 10,000th issuance took over 100ms

My setup is a Node JS app and chain(single node) spun up with docker-compose.

Multichain version is 1.0.5.

I have been using the multichain-node library but also tried my own code to directly talk to the chain. There wasn't much performance difference (my own code was actually a bit slower).

Apologies for the code snippet below but is there something I'm doing wrong? Any help would be appreciated.

async function issue(counter) {
  const assetId = uuid.v4().replace(/-/g, '');
  const metadata = {
    streamId: `streamId-${counter}`,
    cData: `c-${counter}`,
    lData: `l-${counter}`,
    sData: `s-${counter}`,
    mData: `m-${counter}`,
    dateCreated: new Date().toString(),
  };

  const body = JSON.stringify({ jsonrpc: '1.0', id: 'curltest', method: 'issuefrom', params: [MY_ADDRESS, MY_ADDRESS, assetId, 1, 1, 0, metadata] });

  const url = `http://${multichainHost}:8571`;
  const options = {
    url,
    method: 'POST',
    headers:
    {
      'content-type': 'text/plain',
    },
    auth: {
      user: 'user',
      pass: `${multichainPassword}`,
    },
    body,
  };

  const start = now();
  const response = await rp(options);
  const end = now();
  const duration = (end - start).toFixed(1);
  console.log(`${counter}, ${duration}`);
  return response.body;
}

async function directTest() {
  const nToCreate = 10000;
  for (let i = 0; i < nToCreate; i += 1) {
    await issue(i);
  }
}

Performance impact as number of Nodes in Blockchain increase

Mon, 12 Mar 2018 09:53:53 +0000

Hi

We are trying to implement a private blockchain starting with 10 nodes. Going forward we want to expand it to hundreds of nodes.

In our blockchain we want to credit points to user account based on certain action. This has to happen in near real time hence we have performance as one of the most important criteria for selecting blockchain platform.

I understand multichain based blockchain can do around 1000 TPS.

However as we know every commited block in blockchain has to be replicated to all nodes in blockchain network. So if the number of nodes in network increase it would add more latency due to increased number of nodes.

Is this understanding correct? If yes how TPS is affected with increased number of nodes.

Multichain Scalability

Mon, 15 May 2017 04:11:46 +0000

Hi,

I would love to listen from you on the topic 'Scaling with Multichain' - What could be scalability issues with multi-organisation private blockchain setup and how to address them. Also some insights on operational cost.