Hive-Engine Node Benchmark Report - 2025-04-18

in #hive-engine • 6 months ago

Full Hive-Engine API Node Update - (18/04/2025)

2025-04-18T17:00:04 (UTC)
Note: This post is published from the @nectarflower account, but the benchmark data and nodee metadata are from the @flowerengine account.
@nectarflower provides daily updates about the state of all available full API node servers for Hive-Engine.
More information about nectarflower can be found in the github repository.

List of failing nodes

This table includes a list of all nodes which were not able to answer to a getStatus API call within the specified timeout.

nodeerror
https://herpc.meb.asiaNot a valid hive-engine node: HTTPSConnectionPool(host='herpc.meb.asia', port=443): Max retries e...
https://herpc.cupidchat.netNot a valid hive-engine node: HTTPSConnectionPool(host='herpc.cupidchat.net', port=443): Max retr...
https://herpc.mmshare.netNot a valid hive-engine node: HTTPSConnectionPool(host='herpc.mmshare.net', port=443): Max retrie...
https://herpc.asiaworld.netNot a valid hive-engine node: HTTPSConnectionPool(host='herpc.asiaworld.net', port=443): Max retr...
https://herpc.tarwateinthar.comNot a valid hive-engine node: HTTPSConnectionPool(host='herpc.tarwateinthar.com', port=443): Max ...

List of working nodes (At least once)

This table includes all nodes which were able to answer a getStatus call within the timeout. The achieved mean duration values are shown. The returned SSCnodeVersion is also shown.

nodemean time [s]SSCnodeVersion
https://light.primersion.com0.0ivm-1.0.0
https://herpc.dtools.dev0.0ivm-1.0.0
https://heapi.c0ff33a.uk0.0ivm-1.0.0
https://api2.hive-engine.com/rpc0.0ivm-1.0.0
https://herpc.filoz.info0.0ivm-1.0.0
https://herpc.liotes.com0.0ivm-1.0.0
https://he.c0ff33a.uk0.0ivm-1.0.0
https://enginerpc.com0.0ivm-1.0.0
https://he.sourov.dev0.0ivm-1.0.0
https://api.hive-engine.com/rpc0.0ivm-1.0.0
https://he.atexoras.com:20830.0ivm-1.0.0
https://herpc.actifit.io0.0ivm-1.0.0
https://herpc.kanibot.com0.0ivm-1.0.0
https://he.eturnerx.com0.0ivm-1.0.0
https://api.primersion.com0.0ivm-1.0.0
https://engine.hive.pizza0.0ivm-1.0.0

Full Hive-Engine API Node Update - (18/04/2025)

2025-04-18T17:00:04 (UTC)
Note: This post is published from the @nectarflower account, but the benchmark data and node metadata are from the @flowerengine account.
@nectarflower provides daily updates about the state of all available full API node servers for Hive-Engine.
More information about nectarflower can be found in the github repository.

List of failing nodes

This table includes a list of all nodes which were not able to answer to a getStatus API call within the specified timeout.

nodeerror
https://herpc.meb.asiaNot a valid hive-engine node: HTTPSConnectionPool(host='herpc.meb.asia', port=443): Max retries e...
https://herpc.cupidchat.netNot a valid hive-engine node: HTTPSConnectionPool(host='herpc.cupidchat.net', port=443): Max retr...
https://herpc.mmshare.netNot a valid hive-engine node: HTTPSConnectionPool(host='herpc.mmshare.net', port=443): Max retrie...
https://herpc.asiaworld.netNot a valid hive-engine node: HTTPSConnectionPool(host='herpc.asiaworld.net', port=443): Max retr...
https://herpc.tarwateinthar.comNot a valid hive-engine node: HTTPSConnectionPool(host='herpc.tarwateinthar.com', port=443): Max ...

List of working nodes (At least once)

This table includes all nodes which were able to answer a getStatus call within the timeout. The achieved mean duration values are shown. The returned SSCnodeVersion is also shown.

nodemean time [s]SSCnodeVersion
https://light.primersion.com0.0ivm-1.0.0
https://herpc.dtools.dev0.0ivm-1.0.0
https://heapi.c0ff33a.uk0.0ivm-1.0.0
https://api2.hive-engine.com/rpc0.0ivm-1.0.0
https://herpc.filoz.info0.0ivm-1.0.0
https://herpc.liotes.com0.0ivm-1.0.0
https://he.c0ff33a.uk0.0ivm-1.0.0
https://enginerpc.com0.0ivm-1.0.0
https://he.sourov.dev0.0ivm-1.0.0
https://api.hive-engine.com/rpc0.0ivm-1.0.0
https://he.atexoras.com:20830.0ivm-1.0.0
https://herpc.actifit.io0.0ivm-1.0.0
https://herpc.kanibot.com0.0ivm-1.0.0
https://he.eturnerx.com0.0ivm-1.0.0
https://api.primersion.com0.0ivm-1.0.0
https://engine.hive.pizza0.0ivm-1.0.0

Node Uptime Statistics (7-day period)

This table shows how reliable nodes have been over the past week.

nodeuptime %total checks
https://api.hive-engine.com/rpc100.0%1
https://api.primersion.com100.0%1
https://api2.hive-engine.com/rpc100.0%1
https://engine.hive.pizza100.0%1
https://enginerpc.com100.0%1
https://he.atexoras.com:2083100.0%1
https://he.c0ff33a.uk100.0%1
https://he.eturnerx.com100.0%1
https://he.sourov.dev100.0%1
https://heapi.c0ff33a.uk100.0%1
https://herpc.actifit.io100.0%1
https://herpc.dtools.dev100.0%1
https://herpc.filoz.info100.0%1
https://herpc.kanibot.com100.0%1
https://herpc.liotes.com100.0%1
https://light.primersion.com100.0%1
https://herpc.asiaworld.net50.0%2
https://herpc.cupidchat.net50.0%2
https://herpc.meb.asia50.0%2
https://herpc.mmshare.net50.0%2
https://herpc.tarwateinthar.com50.0%2

Token retrieval

This table shows how many token operations were processed by the node within the specified time. The nodes are ordered according to the number of operations processed.

nodeoperations processedoperations per second
https://herpc.filoz.info3414113.8
https://herpc.actifit.io93531.15
https://engine.hive.pizza80626.85
https://heapi.c0ff33a.uk64721.54
https://he.c0ff33a.uk64221.4
https://herpc.liotes.com61720.55
https://herpc.kanibot.com43314.39
https://enginerpc.com10916.47
https://api.primersion.com8856.73
https://he.atexoras.com:2083852.82
https://light.primersion.com5923.14
https://he.sourov.dev5229.65
https://he.eturnerx.com3812.3
https://api2.hive-engine.com/rpc156.17
https://api.hive-engine.com/rpc146.47
https://herpc.dtools.dev1331.97

Contract operations

This table shows how many contract operations were processed by the node within the specified time. The nodes are ordered according to the number of operations processed.

nodeoperations processedoperations per second
https://herpc.filoz.info3163105.41
https://herpc.actifit.io82327.41
https://engine.hive.pizza75725.21
https://he.c0ff33a.uk73824.59
https://heapi.c0ff33a.uk73324.4
https://herpc.liotes.com61220.37
https://herpc.kanibot.com40113.37
https://enginerpc.com9718.14
https://he.atexoras.com:2083943.12
https://he.sourov.dev5237.78
https://he.eturnerx.com2715.67
https://api.hive-engine.com/rpc147.18
https://api2.hive-engine.com/rpc148.08
https://herpc.dtools.dev1234.32

Account history operations

This table shows how many account history operations were processed by the node within the specified time. The nodes are ordered according to the number of operations processed.

nodeoperations processedoperations per second
https://herpc.kanibot.com1163.84
https://herpc.filoz.info191.77
https://api.hive-engine.com/rpc111.49
https://engine.hive.pizza30.75
https://herpc.mmshare.net20.71
https://he.sourov.dev20.81
https://herpc.tarwateinthar.com20.68
https://enginerpc.com21.01
https://herpc.meb.asia10.55
https://api.primersion.com10.51
https://herpc.dtools.dev10.55
https://herpc.cupidchat.net10.54
https://herpc.asiaworld.net10.55
https://herpc.actifit.io10.53
https://api2.hive-engine.com/rpc10.54
https://he.c0ff33a.uk10.5
https://he.eturnerx.com10.51
https://heapi.c0ff33a.uk10.55
https://light.primersion.com10.54
https://herpc.liotes.com10.55
https://he.atexoras.com:208310.51

Latency

This table shows the latency measurements for each node. The nodes are ordered according to average latency (lowest first).

nodeavg latency [s]min latency [s]max latency [s]
https://herpc.filoz.info0.030.010.05
https://herpc.dtools.dev0.040.010.07
https://api.primersion.com0.050.020.1
https://light.primersion.com0.060.040.09
https://herpc.actifit.io0.060.050.08
https://he.sourov.dev0.060.050.1
https://engine.hive.pizza0.10.050.13
https://enginerpc.com0.10.080.13
https://herpc.kanibot.com0.10.040.15
https://api.hive-engine.com/rpc0.110.040.15
https://he.eturnerx.com0.120.10.13
https://api2.hive-engine.com/rpc0.120.050.15
https://he.c0ff33a.uk0.120.040.17
https://herpc.liotes.com0.120.050.16
https://heapi.c0ff33a.uk0.130.050.16
https://he.atexoras.com:20830.670.31.19

Node Trends and Reliability

The following data shows trends over the past 7 days:

Node Uptime

NodeUptime %Total Runs
https://api.hive-engine.com/rpc100.0%1
https://api.primersion.com100.0%1
https://api2.hive-engine.com/rpc100.0%1
https://engine.hive.pizza100.0%1
https://enginerpc.com100.0%1
https://he.atexoras.com:2083100.0%1
https://he.c0ff33a.uk100.0%1
https://he.eturnerx.com100.0%1
https://he.sourov.dev100.0%1
https://heapi.c0ff33a.uk100.0%1
https://herpc.actifit.io100.0%1
https://herpc.dtools.dev100.0%1
https://herpc.filoz.info100.0%1
https://herpc.kanibot.com100.0%1
https://herpc.liotes.com100.0%1

Notable Trends

No significant trends detected in the past 7 days.

Node Consistency

This section shows how consistent each node's performance has been.
Lower standard deviation indicates more consistent performance.

NodeConsistency Score (lower is better)

Conclusion

This report provides a snapshot of Hive-Engine node performance. Users can use this information to select reliable nodes for their applications.

The benchmark data is also available in JSON format in the @flowerengine account's json_metadata for automated processing.

Generated by the engine-bench tool.

#benchmark #nodes #performance #api
6 months ago in #hive-engine by
$3.18
  • Past Payouts $3.18
  • - Author $1.59
  • - Curators $1.59
45 votes
Reply 14
Sort:  
  • Trending
    • [-]
     6 months ago  

    Interesting... didn't know about this. Some feedback!

    • Can you please indicate where you are making the calls (IP or country perhaps)... all benchmarks are relative to sources.
    • "were processed by the node within the specified time." - How much is this specified time?
    • It says "The following data shows trends over the past 7 days:" but then the number of runs shows 1... should it be instead the number of total successful runs in the 7 days divided by the total number of runs planned to do in 7 days?
    • Can you add the command being used to get "Latency" results? I am assuming it's just getStatus, but it's nice to have it clear. Same sort of thing for the other results.

    Anyhow, my diagonal. Let me know what you think.

    [-]
     6 months ago (edited) 

    I'll try to answer the questions in order.

    • Frankfurt Germany - Digital Ocean Droplet
    • It should state that, since it's variable it was vague, but I'll clarify, but the standard tests are 30 second timeout / time limit
    • I was originally running it on my dev machine, That was the first run from the server, it should populate over the week. If it's still not right this time next week, will adjust as needed, but you are probably right, I wasn't sure exactly how I wanted the trends section to be, so if any of them need it badly, that's one that will get refactored.
    • Latency is the average time of 5 samples of:
    start_time = time.time()
# Make a simple query to measure latency - use a lightweight call
api.find("tokens", "tokens", {"symbol": "SWAP.HIVE"}, limit=1)
latency = time.time() - start_time

    I would love some more input, kind of went into this blindly, and the original intent was to do what we did with @nectarflower with @flowerengine, which was run a benchmark every hour and store the results in the account metadata.

    curl -s --data '{"jsonrpc":"2.0", "method":"database_api.find_accounts", "params": {"accounts":["flowerengine"]}, "id":1}' https://api.hive.blog | jq '.result.accounts[0].json_metadata | fromjson' | jq '.nodes[]'

    @nectarflower runs on the :00 minute mark, and @flowerengine runs on the :30 minute mark, to avoid clash. Both benchmarks take ~10 minutes to do all the servers.

    Would absolutely be thrilled to get a PR if you see something that could be done better. Also, I am aware the head section of this post was printed twice, that should be fixed on the next run, don't know how I didn't catch that the first 20 times I ran it.

    [-]
     6 months ago  

    Thanks for the answers. I would love to do more PR's, but lately, time to reply is already a luxury. I will keep giving this a watch and provide any feedback, and if I find anyone keep on helping out, will point he/she in your direction.

    I have noticed also you guys used python 3.13 (which is very recent). Would be nice to support older versions, but its not a problem if not. As in a few months, all pythons everywhere will be supporting 3.13 anyhow.

    Just a thought.

    [-]
     6 months ago  

    I appreciate the feedback just as much as a pull requests.

    It just happens to be the version i'm using, there is no 3.13 specific features being used, should work without problems back several versions (i've tested 3.11, and 3.12)

    [-]
     6 months ago  

    Not for those... but for 3.10 there is. Close enough though =)

    Unfortunately, Ubuntu 22 is still behind. Plus a couple of other Linux distros... either way this would need to be changed on the repo.

    $ cat src/engine_bench/__init__.py
"""Nectar-bench package for benchmarking hive-engine nodes using nectarengine."""

import sys

__version__ = "0.2.0"

# Check Python version
if sys.version_info < (3, 13):
    print("Error: engine-bench requires Python 3.13 or higher")
    sys.exit(1)

    I can install 3.X whatever but just thinking on people that are just using Linux distributed versions.

    I am pushing because I see good stuff... not because I dislike stuff. 😎😍

    [-]
     6 months ago  

    good catch, i'll destroy that section in both benchmarks

    [-]
     6 months ago (edited) 

    This is fantastic feedback!!!!!

    (Its very new still, but will fill out 7 days...over next 7 days 😅)

    [-]
     6 months ago  

    Going to run from my server to see the difference... I was just watching the repo code now... and I think a couple of things will be massively different because of the total timeout being a limit on calls.

    But hey, this is really cool! Love benchmarks because it's part of what I do in real life.

    [-]
     6 months ago  

    We also accept PRs!!! But I know GM will check out your feedback tomirrow!

    [-]
     6 months ago  


    Your comment is upvoted by @topcomment

    Info - Support - Discord

    image.png
    Curated by friendlymoose

    $0.00
      Reply
      [-]
       6 months ago  

      Congratulations @nectarflower! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)

      You received more than 400 upvotes.
      Your next target is to reach 500 upvotes.

      You can view your badges on your board and compare yourself to others in the Ranking
      If you no longer want to receive notifications, reply to this comment with the word STOP

      $0.00
        Reply