<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>0xJan</title>
        <link>https://paragraph.com/@0xjan</link>
        <description>modular is future.</description>
        <lastBuildDate>Thu, 04 Jun 2026 11:35:48 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Performance Analysis of Vultr-based Celestia Lightweight Nodes]]></title>
            <link>https://paragraph.com/@0xjan/performance-analysis-of-vultr-based-celestia-lightweight-nodes</link>
            <guid>PZUy9jzpcY2mQESXmPBe</guid>
            <pubDate>Sat, 29 Apr 2023 06:10:58 GMT</pubDate>
            <description><![CDATA[Operating environment, VPS: Vultr OS: Ubuntu 22.04 x64 Memory: 2 GB RAM CPU: 1 AMD VCPU Disk: 50 GB SSD Hello, I deployed a light node of Celestia using Vultr, in fact for the analysis I will look at two aspects. The tools used to install: sudo apt install iftop First, I use the htop command to monitor CPU, swap memory and disk usage, and df -h to see some basic information about the disk. Using these commands gave me an idea of the system resources consumed by the Celestia light node when it...]]></description>
            <content:encoded><![CDATA[<p>Operating environment,</p><p>VPS: Vultr OS: Ubuntu 22.04 x64 Memory: 2 GB RAM CPU: 1 AMD VCPU Disk: 50 GB SSD</p><p>Hello, I deployed a light node of Celestia using Vultr, in fact for the analysis I will look at two aspects.</p><p>The tools used to install: <code>sudo apt install iftop</code></p><p>First, I use the htop command to monitor CPU, swap memory and disk usage, and <code>df -h</code> to see some basic information about the disk. Using these commands gave me an idea of the system resources consumed by the Celestia light node when it was running. From the results generated by these commands, we can clearly see that the node is currently running very healthy and meets the official requirements for bandwidth and node online frequency.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/a5d676d758184301420759efb8dc1b66d1e81514ef57451ce6dad1498f2c21ef.png" alt="htop" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">htop</figcaption></figure><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/a0b61a1a73f276714eee1570837e5ef8c60f640d21db6e592084d347ad73ac83.png" alt="df" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">df</figcaption></figure><p>Secondly, I checked the online time of the nodes by <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://tiascan.com/">Tiascan</a>, both authentication nodes, bridge nodes, full storage nodes and light nodes can check the uptime of Tiascan very easily.</p><p>Finally, I also used the analysis log provided by Vultr to get a more friendly view of the entire server, including CPU, network bandwidth, and disk usage, which gives a clearer picture of the hardware resources used by the Celestia light node, thus helping me to better understand its performance and operation.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/92ac8368c2ac3452aaee29424ca061f32a55643b0b26da812dea563cdd61408e.png" alt="cpu" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">cpu</figcaption></figure><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/955c13b63e1f36855074d2c78cf34c49f95a17157b7e81490ed1695a6da0fab8.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Conclusion: based on the monitoring results of these tools, I came to a more detailed analysis to understand the hardware performance and bandwidth of the running Celestia light node throughout its operation.</p><p>My github:</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/modular-blockchain/Celestia-PayForBlob-Transaction">https://github.com/modular-blockchain/Celestia-PayForBlob-Transaction</a></p>]]></content:encoded>
            <author>0xjan@newsletter.paragraph.com (0xJan)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/6bdf886645696f315eeadf6d42fc08b86e0bfcebe622d70e2652bc38a6f71e0b.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>