Subnet Management - csyj4 (Application)

Governance NNS proposal discussions
, ,
1

This topic is intended to capture Subnet Management activities over time for the csyj4 subnet, providing a place to ask questions and make observations about the management of this subnet.

At the time of creating this topic the current subnet configuration is as follows:

Expand 
{
  "version": 44965,
  "records": [
    {
      "key": "subnet_record_csyj4-zmann-ys6ge-3kzi6-onexi-obayx-2fvak-zersm-euci4-6pslt-lae",
      "version": 44965,
      "value": {
        "membership": [
          "i4zve-soi3o-vqbql-gklv5-dbklt-g43ha-k3ju6-vdlrf-5t6lu-pyl3j-xqe",
          "k4ecc-uo6mt-3jzeo-axsrf-fm4s4-2v2fo-f2hai-nhbm7-ktblp-aixvz-iae",
          "cupz3-ehtqa-su3yl-2shoq-7yxw5-25uhz-g5kew-73dpi-w4gpu-hsmoi-vqe",
          "5az5s-5xxrd-ip5m2-6ps3s-uptc2-mz5gh-5ntqe-bmu7p-bhdyu-x4hu3-dae",
          "g3ug2-wz6kb-unyk6-6mj4f-halk3-kkfvi-k33iz-fftob-qipom-t4kzr-qqe",
          "kno7y-tdoxx-da524-svbxm-wt7xn-nyit3-vtsd4-nimle-vahxa-q65e6-oqe",
          "5s6r2-75ps5-mkxnk-litjj-szhkg-wanvq-jwuly-drl6j-ldie7-2ols7-yae",
          "wbqzc-cvi3c-gnuak-ztcqs-j4ga3-6m64f-w2fmy-qjqve-lzvja-rfir7-kae",
          "elons-ke2ex-4ykad-warsf-bi7zm-oskxc-un44b-phznq-sovqe-ko6u3-nqe",
          "3smci-63tqe-6q5xc-wpdmj-pnhan-own4t-6km2r-77mfh-c2h7d-xzunk-cqe",
          "6t3hc-abwek-snx4i-s57g2-w7u2g-beaec-jsjgx-g47s7-zjeb2-cb5pu-yqe",
          "zcxej-wovzy-rxnvs-bcz3a-ruh4s-a3blo-24ej7-izr7h-toic5-ix5gu-qqe",
          "pptbq-moz46-a4j7y-njscm-t3d3o-wj2pz-3vbak-4fqnt-trxz6-f4fg7-eae"
        ],
        "nodes": {},
        "max_ingress_bytes_per_message": 2097152,
        "max_ingress_messages_per_block": 1000,
        "max_block_payload_size": 4194304,
        "unit_delay_millis": 1000,
        "initial_notary_delay_millis": 600,
        "replica_version_id": "b0ade55f7e8999e2842fe3f49df163ba224b71a2",
        "dkg_interval_length": 499,
        "start_as_nns": false,
        "subnet_type": "verified_application",
        "features": {
          "canister_sandboxing": false,
          "http_requests": true,
          "sev_enabled": false
        },
        "max_number_of_canisters": 120000,
        "ssh_readonly_access": [],
        "ssh_backup_access": [],
        "ecdsa_config": null,
        "chain_key_config": null
      }
    }
  ]
}
2

Proposal 132218

This proposal sets the notarisation delay of the subnet to 300ms, down from 600ms. The change will increase the block rate of the subnet, aimed to reduce latency of update calls.

This is the same subnet config update that was applied to the canary subnet last week, which has held a steady and impressive block rate since. More context is available here → Reducing End to End latencies on the Internet Computer

Here are the current metrics for this subnet. A question I’ll be asking on the Subnet Management General thread (see reference below this post) is why this update is being rolled out to so many subnets at once, each with different finalisation rate and transaction profiles (e.g. peaks and troughs, whereas the canary subnet was always steady, even prior to the update). I’m wondering if this limits the representativeness of the results on that canary subnet.

image
image1250×729 75.8 KB