Benchmark: dsteem vs steem-js round 2

HTML Preparation code:

<script src="//unpkg.com/dsteem@^0.8.1/dist/dsteem.js"></script>
<script src="//cdn.steemjs.com/lib/latest/steem.min.js"></script>

Script Preparation code:

var tx = {
    ref_block_num: 1234,
    ref_block_prefix: 445566,
    expiration: '2017-07-09T10:00:00.000',
    operations: [['vote', {
        voter: 'foo',
		author: 'bar',
        permlink: 'i-like-turtles',
        weight: 10000
    }]],
    extensions: [],
	signatures: []
}
var keyWif = '5JQy7moK9SvNNDxn8rKNfQYFME5VDYC2j9Mv2tb7uXV5jz3fQR8'

var dsteemKey = dsteem.PrivateKey.fromString(keyWif)
var dsteemClient = new dsteem.Client()

var steemjsKey = {posting: keyWif}

Tests:

dsteem sign tx
dsteemClient.broadcast.sign(tx, dsteemKey)
steem-js sign tx
steem.auth.signTransaction(tx, steemjsKey)
dsteem wif to public
dsteem.PrivateKey.from(keyWif).toPublic()
steem-js wif to public
steem.auth.wifToPublic(keyWif)

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
dsteem sign tx
steem-js sign tx
dsteem wif to public
steem-js wif to public

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated 28 days ago):

LLMs can make mistakes. Check important info.

Measuring the performance of JavaScript libraries and their approaches can be quite nuanced, as it involves understanding the intricacies of how these libraries handle different aspects of programming such as key management, network communication, and more.

The benchmark provided is comparing two JavaScript libraries: `dsteem` and `steem-js`. Both libraries seem to provide an interface for interacting with the Steemit blockchain.

### dsteem

1. **Library Purpose**: The primary purpose of `dsteem` seems to be providing a full-featured Steemit blockchain client library.

2. **Options Compared**:
   - `broadcast.sign(tx, dsteemKey)`: This method is used for signing transactions on the blockchain.
   - `dsteem.PrivateKey.from(keyWif).toPublic()`: This method converts a key from WIF format to public format.

3. **Pros and Cons of Approaches**:
   - Signing transactions involves serializing operations into a transaction object (`tx`), which is then signed with the private key, and this process can be time-consuming depending on factors like network latency.
   - Converting keys (WIF to Public) generally requires less computational effort compared to signing transactions because it does not involve actual blockchain operations.

4. **Other Considerations**: When choosing between these methods for performance-critical applications, the primary consideration is usually how much of the processing time can be attributed to signature generation versus other aspects like network latency and parsing operations.

### steem-js

1. **Library Purpose**: The `steem-js` library seems designed primarily with simplicity and ease of use in mind, particularly tailored for developers who want to integrate Steemit blockchain functionality without delving into the intricacies of blockchain interaction directly.

2. **Options Compared**:
   - `auth.signTransaction(tx, steemjsKey)`: This method is used for signing transactions on the blockchain.
   - `auth.wifToPublic(keyWif)`: This method converts a WIF key to public format.

3. **Pros and Cons of Approaches**:
   - Similar considerations apply as with `dsteem` (signing vs key conversion), but often `steem-js` might offer simpler interfaces due to its emphasis on ease of use, which could lead to more efficient execution times in certain scenarios.

4. **Other Considerations**: When choosing between these libraries for performance-critical applications, the choice largely depends on how well each library performs the necessary operations without introducing too much overhead that might outweigh the benefits it provides.

### Other Alternatives

- **Official Steemit API**: If you're looking at integrating directly with the Steemit blockchain for operations like transaction signing and key conversion, using the official API provided by Steemit might offer a direct interface to these functionalities.
- **Other Blockchain Client Libraries**: There are other libraries available that provide similar functionalities to `dsteem` and `steem-js`, such as `steem-rs` for Rust. Choosing one of these can depend on the specific needs of your application, including performance requirements, ease of use, and compatibility with different platforms.

In summary, when choosing between `dsteem` and `steem-js`, or any other library for that matter, the key factors to consider are the specific functionalities needed (like signing transactions), performance overhead, ease of development, and compatibility.

Latest run results:

Run details: (Test run date: 5 years ago)

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Browser/OS: Firefox 69 on Windows

View result in a separate tab

Test name	Executions per second
dsteem sign tx	401.9 Ops/sec
steem-js sign tx	12.5 Ops/sec
dsteem wif to public	0.0 Ops/sec
steem-js wif to public	76.6 Ops/sec

Related benchmarks:

dsteem vs steem-js round 2 (version: 0)

FIGHT

Comparing performance of: dsteem sign tx vs steem-js sign tx vs dsteem wif to public vs steem-js wif to public

Created: 7 years ago by: Guest

Jump to the latest result

dsteem sign tx

steem-js sign tx

dsteem wif to public

steem-js wif to public

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated 28 days ago):