From ef905ead8910cefec2bae4ede27204126b214886 Mon Sep 17 00:00:00 2001 From: guillaumemichel Date: Thu, 26 Sep 2024 15:19:34 +0200 Subject: [PATCH] removed IPNI plot in KPIs --- content.en/ipfs/kpi/_index.md | 23 +++++++++-------------- 1 file changed, 9 insertions(+), 14 deletions(-) diff --git a/content.en/ipfs/kpi/_index.md b/content.en/ipfs/kpi/_index.md index 6c64f781a5..d74967995a 100644 --- a/content.en/ipfs/kpi/_index.md +++ b/content.en/ipfs/kpi/_index.md @@ -7,7 +7,7 @@ aliases: --- # IPFS KPIs -IPFS relies on the coordinated participation of a swarm of independent peers to function correctly. Therefore, measuring the performance and health of the network is crucial for ensuring its reliability and efficiency. In this context, we summarise a number of network characteristics as key performance indicators. +IPFS relies on the coordinated participation of a swarm of independent peers to function correctly. Therefore, measuring the performance and health of the network is crucial for ensuring its reliability and efficiency. In this context, we summarise a number of network characteristics as key performance indicators. Our KPIs are currently focusing primarily on the public [IPFS DHT](https://docs.ipfs.tech/concepts/dht/) (although we do report on other parts of the architecture too). Understanding that IPFS is an ecosystem of [content routing subsystems](https://docs.ipfs.tech/concepts/how-ipfs-works/#subsystems-overview), over time, we plan to expand to other content routing subsystems too. ## Network Size & Stability @@ -22,17 +22,16 @@ The total number of peers in the network is estimated using the number of unique The total number of unique software agents operating in the network is estimated from those seen by Protocol Labs' [bootstrap nodes](https://docs.ipfs.tech/concepts/glossary/#bootstrap-node) when a peer connects. The number of unique agents seen by the [Nebula crawler](/tools/nebula/) when crawling the IPFS DHT is included for comparison. The software agent strings have not been refined or processed, resulting in the count treating major and minor versions of each software agent as distinct entries. - {{< plotly json="../../plots/latest/ipfs-unique-agents.json" height="400px" >}} - -## Content Routing +## Content Routing IPFS employs several content routing subsystems, with the [Kademlia](https://docs.ipfs.tech/concepts/dht/#kademlia) Distributed Hash Table (DHT) being the most established. Within the network, peers commonly use this system to locate other peers that hold the content being requested. We measure the availability of DHT server nodes and the latency of [DHT lookups](https://docs.ipfs.tech/concepts/dht/#lookup-algorithm) for random content. ### DHT server availability We categorize [DHT Server](https://docs.ipfs.tech/concepts/dht/#routing-tables) nodes with regard to their "availability" as follows: + - "Online": the node has been found online for 80% of time or more. - "Mostly Online": the node has been found online between 40%-80% of time. - "Mostly Offline": the node has been found online between 10%-40% of time. @@ -44,7 +43,6 @@ Data is collected using the [Nebula crawler](/tools/nebula/). {{< plotly json="../../plots/latest/dht-availability-classified-current.json" height="250px" >}} - #### DHT Server Availability, classified over time {{< plotly json="../../plots/latest/dht-availability-classified-overall.json" height="600px" >}} @@ -63,12 +61,12 @@ The historic trend over time is currently provided by [Parsec](/tools/parsec). B {{< plotly json="../../plots/latest/dht-lookup-performance-long.json" height="600px" >}} -### IPNI utilization - -[IPNI](https://github.com/ipni) is a set of protocols that describe how data can be indexed across the IPFS and Filecoin networks. Network indexers complement the [IPFS DHT](https://docs.ipfs.tech/concepts/dht/) to enable peers to locate content-addressed data. The data in the plot below shows the number of requests made per day to the network indexers operated by [cid.contact](https://cid.contact/). - -{{< plotly json="../../plots/latest/ipni-requests-overall.json" height="600px" >}} - + + + + + + ## Websites @@ -78,7 +76,6 @@ A common use-case for IPFS is hosting websites, addressed using [IPNS](https://d {{< plotly json="../../plots/latest/websites-ttfb-quartiles.json" height="250px" >}} - ## HTTP Gateway Usage #### Gateway Requests @@ -86,5 +83,3 @@ A common use-case for IPFS is hosting websites, addressed using [IPNS](https://d The following plot shows the total number of requests made per day to the ipfs.io, the main domain at [public IPFS gateway](https://docs.ipfs.tech/concepts/public-utilities/#public-ipfs-gateways) operated by [Interplanetary Shipyard](https://ipshipyard.com/). Data is collated from nginx access logs that front the gateway infrastructure and currently does not include requests made to less popular dweb.link and trustless-gateway.link domains. {{< plotly json="../../plots/latest/gateway-requests-overall.json" height="600px" >}} - -