AELF vs Ethereum – aelf –

1. Test Case and Code
2. Machine Configuration
3. Test Results
3.1 EVM
3.2 AELF
3.2.1 LoopDivAdd10M
3.2.2 LoopExpNop1M

As the development of aelf network matures, various types of tests are being conducted to pressure test the performance of the network in a number of different angles.

One of the more recent tests to check the advanced nature of the fundamental underlying technology of aelf, was to compare the performance of both Ethereum and aelf under identical environment.

The results were stunning. aelf’s contract execution efficiency was proven to be substantially higher than that of Ethereum’s EVM, aelf outpacing Ethereum by hundreds if not thousands of times in processing speed. Ethereum utilizes its EVM module to support contract execution while its 256 bit stack size and gas count contribute significantly to the overall performance. In contrast, aelf calls the contract through C# reflection allowing many unnecessary executions to be bypassed.

1. Test Case and Code

The test was conducted using Ethereum loop-DivAdd-10M.json and loop-exp-nop-1M.json.

ETH: Based on the official go implementation version https://github.com/ethereum/go-ethereum

AELF: Based on the official C# implementation version https://github.com/AElfProject/AElf

Test case, standard test for ETH： https://github.com/ethereum/tests/tree/develop/src/VMTestsFiller

Corresponding aelf test program：https://github.com/AElfProject/AElf/blob/dev/bench/AElf.Benchmark

2. Machine Configuration

Test Enviornment:
OS=ubuntu 16.04
QEMU Virtual CPU, 2 CPU, 2 logical and 2 physical cores
CPU MHz: 2194.916; cache size : 16384 KB

aelf Test Environment:

BenchmarkDotNet=v0.11.5
.NET Core SDK=2.2.203
[Host] : .NET Core 2.2.4 (CoreCLR 4.6.27521.02, CoreFX 4.6.27521.01), 64bit RyuJIT DEBUG

3. Test Results

LoopDivAdd10M: EVM takes 169 times longer than aelf

LoopExpNop1M: EVM takes 1223 times longer than aelf

3.1 EVM

The official go implementation version of the built-in test program execution results are as shown below.

LoopDivAdd10M：14.236813572s

LoopExpNop1M: 639.16568ms

3.2 AELF

LoopDivAdd10M: 84.01ms

LoopExpNop1M: 0.5225ms

3.2.1 LoopDivAdd10M

Dividing/Addition cycle 10 million times

Method:

public override DoubleValue LoopDivAdd(DivAddTestInput input)

return new DoubleValue ;
}

Input:

new DivAddTestInput()

Result:

3.2.2 LoopExpNop1M

Method

public override Int32Value LoopExpNop(PerformanceTesteInput input)

return new Int32Value ;
}

Input

new PerformanceTesteInput()

Result:

In the case of the same test machine configuration, 10 million cycles of addition and division test, aelf only needs 84.01ms, 169 times higher than Ethereum EVM; 1 million empty loop Secondly, aelf only needs 0.5225 ms, which is 1223 times higher than Ethereum EVM.

When we just got the result of 500us, we were also surprised, it took 5ms to run this test program before. We thought it was because of this release, the optimization of this empty loop code. However, after decompilation, the corresponding logic is still there, and the data has no problem.

Published at Sun, 12 May 2019 11:12:10 +0000

July 20, 2017

SegWit or Not, Bitfury is Ready for Lightning With Successful Bitcoin Main Net Test

While Segregated Witness (SegWit) activation is looking more likely by the hour, Bitfury is getting ready to deploy a version of the Lightning network with or without the protocol upgrade.

The blockchain technology company, perhaps best known for its bitcoin mining pool of the same name, successfully sent real bitcoins over a test version of the Lightning Network this week. Interestingly, Bitfury’s implementation of the technology is compatible with the current bitcoin protocol and is therefore functional even without SegWit.

“This is a major accomplishment by our technical team and an important step forward for the Lightning Network and the growth of bitcoin,” Valery Vavilov, CEO of The Bitfury Group, said in a statement.

Lightning Network

The Lightning Network is a highly anticipated second-layer scaling solution that allows for cheap and instant (micro)payments. Cleverly leveraging bitcoin’s basic scripting capabilities, Lightning users should be able to make a virtually unlimited number of transactions, where only a minimal proportion of them are recorded on bitcoin’s blockchain, thereby boosting bitcoin’s scalability. Meanwhile, all users remain in control of their own bitcoins at all times, maintaining the trustless properties of bitcoin itself.

“The Lightning Network has the potential to solve bitcoin’s scalability issue and provide instant payment functionality. By demonstrating that the Lightning Network can function now, Bitfury has cleared the way to increased transaction processing and further adoption of bitcoin,” Vavilov said.

Bitfury’s Lightning implementation is based on LND, which is being developed by Lightning Labs.

For its demo, the Bitfury software team created two Lightning transactions. One of these is a straight transaction from one Lightning node to the next, effectively simulating a payment channel between two users. Since it was only a test, Bitfury only made one transaction — but it could have made thousands back and forth at no extra cost.

The other test was a single-hop transaction, which better simulates the main purpose of the Lightning Network. Users pay each other through a mutual third party, without requiring any trust in this third party. While the Bitfury software team only made one transaction on this channel as well, it could, once again, have made thousands back and forth between all three parties, at no extra cost.

Since Bitfury’s test took place on the main net, the funding and settlement transactions are recorded on bitcoin’s blockchain and can be seen by any typical block explorer.

Tests and SegWit

Bitfury’s is not the first successful test of the Lightning Network. Several companies, including Lightning Labs, Blockstream, ACINQ as well as Bitfury itself have experimented with their implementations of the technology. But since most of these companies are working on versions of Lightning that rely on Segregated Witness, these tests were limited to bitcoin’s testnet and Litecoin. Likewise, major wallet service Blockchain has sent “Thunder” transactions over bitcoin’s main net. But while Thunder resembles the Lightning protocol, it isn’t quite as trustless or decentralized.

As such, Bitfury is the first company to get a version of the Lightning Network up and running on the current bitcoin protocol.

“We released this first experimental version of the Lightning Network for bitcoin because we think the Lightning Network is an essential technology for bitcoin and would love to see it made available as soon as possible,” Vavilov said. “We are proud that our developers found a way to adopt the Lightning Network for bitcoin without SegWit. It’s a huge step forward for bitcoin scalability.”

Regardless, the CEO noted that he is hopeful that SegWit will activate on the bitcoin network. With BIP91 currently getting close to its activation threshold, it seems increasingly likely that SegWit could be live within a month. This would allow for a version of the Lightning Network that offers an improved user experience.

Vavilov:

“The Lightning Network will be the most effective when used with SegWit, which is why we are fully committed to SegWit’s implementation, and we will continue working on a version of the Lightning Network that is compatible with SegWit.”

Bitfury, which started out as a bitcoin miner, has grown to become one of the largest private infrastructure providers in the Blockchain ecosystem. Part of this effort, the company has been supporting the development and implementation of the Lightning Network for well over a year. Bitfury previously also co-designed and successfully tested Flare, a payment-routing solution for the Lightning Network.

Watch the video of Bitfury’s tests here:

[youtube https://www.youtube.com/watch?v=fqT-3xN8npA?feature=oembed&w=480&h=270]

The post SegWit or Not, Bitfury is Ready for Lightning With Successful Bitcoin Main Net Test appeared first on Bitcoin Magazine.