<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Posts on Aleksei Riumin | Senior Infrastructure Architect</title><link>https://lxryumin-best.github.io/posts/</link><description>Recent content in Posts on Aleksei Riumin | Senior Infrastructure Architect</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 17 Jun 2026 12:00:00 +0300</lastBuildDate><atom:link href="https://lxryumin-best.github.io/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating a Senior Architect's Portfolio: Hugo, GitHub Pages, and AI</title><link>https://lxryumin-best.github.io/posts/17062026_hugo_portfolio_automation/</link><pubDate>Wed, 17 Jun 2026 12:00:00 +0300</pubDate><guid>https://lxryumin-best.github.io/posts/17062026_hugo_portfolio_automation/</guid><description>How to build a zero-maintenance, blazingly fast portfolio using Hugo, GitHub Actions, VS Code, and Claude Opus 4.6 as an automated translator and technical writer.</description></item><item><title>Mitigating 99% Disk Exhaustion Caused by AI &amp; SEO Scrapers</title><link>https://lxryumin-best.github.io/posts/17062026_highloadbottrafficmitigation/</link><pubDate>Wed, 17 Jun 2026 12:00:00 +0300</pubDate><guid>https://lxryumin-best.github.io/posts/17062026_highloadbottrafficmitigation/</guid><description>How we resolved a critical server disk space issue on a high-traffic sports portal by identifying and blocking aggressive AI bots and SEO crawlers.</description></item><item><title>Seamless Bare-Metal Migration: NVMe Lift-and-Shift Between Identical Nodes</title><link>https://lxryumin-best.github.io/posts/16062026_baremetal_nvme_migration/</link><pubDate>Tue, 16 Jun 2026 11:31:39 +0300</pubDate><guid>https://lxryumin-best.github.io/posts/16062026_baremetal_nvme_migration/</guid><description>How to execute a fast bare-metal hardware swap using NVMe migration on identical chipsets, mitigating TPM, Secure Boot, and network configuration conflicts.</description></item><item><title>Physics vs. Marketing: Real AV1300 PowerLine Speeds on Old Aluminum Wire</title><link>https://lxryumin-best.github.io/posts/15062026_powerline_aluminum_mesh_bridge/</link><pubDate>Mon, 15 Jun 2026 12:00:00 +0300</pubDate><guid>https://lxryumin-best.github.io/posts/15062026_powerline_aluminum_mesh_bridge/</guid><description>How to salvage a remote network link when underground conduits fail. Testing TP-Link AV1300 over 2-core aluminum and optimizing IP cameras for constrained links.</description></item><item><title>Cost-Effective Kubernetes: Hardware Isolating Dev &amp; Prod Environments in a Single Cluster</title><link>https://lxryumin-best.github.io/posts/15062026_kubernetes_node_affinity_dev_prod/</link><pubDate>Mon, 15 Jun 2026 10:00:00 +0300</pubDate><guid>https://lxryumin-best.github.io/posts/15062026_kubernetes_node_affinity_dev_prod/</guid><description>Learn how to use Kubernetes Node Affinity to safely run Development and Production environments within a single cluster, saving B2B infrastructure costs.</description></item><item><title>Proxmox Server Crash: Recovering XFS Data After a Catastrophic NVMe Failure</title><link>https://lxryumin-best.github.io/posts/14062026_proxmox_nvme_crash_recovery/</link><pubDate>Sun, 14 Jun 2026 22:41:25 +0300</pubDate><guid>https://lxryumin-best.github.io/posts/14062026_proxmox_nvme_crash_recovery/</guid><description>How to handle a sudden NVMe controller failure in Proxmox VE. Step-by-step XFS troubleshooting, read-only data salvage, and hardware migration.</description></item><item><title>Welcome to My Digital Garden: Infrastructure &amp; DevOps</title><link>https://lxryumin-best.github.io/posts/welcome/</link><pubDate>Sun, 14 Jun 2026 12:00:00 +0300</pubDate><guid>https://lxryumin-best.github.io/posts/welcome/</guid><description>About my expertise as an Infrastructure Architect, System Administrator, and Independent IT Consultant — from network engineering to cloud-native solutions.</description></item><item><title/><link>https://lxryumin-best.github.io/posts/21062026_workstation_upgrade_rtx3080_throttling/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lxryumin-best.github.io/posts/21062026_workstation_upgrade_rtx3080_throttling/</guid><description>&lt;p>title: &amp;ldquo;Architect&amp;rsquo;s Workstation Upgrade &amp;amp; RTX 3080 Thermal Throttling Analysis&amp;rdquo;
date: 2026-06-21T12:00:00+03:00
draft: false
description: &amp;ldquo;Upgrading a local infrastructure architect&amp;rsquo;s lab. Diagnosing severe RTX 3080 thermal throttling and planning VRM/VRAM maintenance to restore 320W TDP.&amp;rdquo;
tags: [Hardware, Workstation, RTX3080, Troubleshooting]
The Context (Business Challenge / Problem):
Maintaining an optimal local environment is critical for an Infrastructure Architect working with Proxmox, Docker, and preparing for the CKA (Kubernetes) certification. I recently migrated my primary workstation to an Intel Core i5-12400 with 32GB of DDR4—currently the most cost-effective platform for running virtualized local labs. However, during stress testing, the Palit RTX 3080 GPU exhibited severe thermal throttling. Instead of operating at its design power envelope of 320W-330W under heavy load, the card drastically downclocked, dropping power consumption to just 140W to prevent critical silicon damage.
The Architecture &amp;amp; Work (Solution):
The core platform rebuild was a success, providing a stable and highly efficient foundation for complex routing and containerized workloads. To address the GPU bottleneck, I analyzed the hardware telemetry. The issue stems from degraded thermal pads on the GDDR6X memory modules and VRM. GDDR6X runs notoriously hot, and once it hits the 105°C+ junction temperature limit, the firmware aggressively throttles performance. The engineering solution requires a complete teardown of the cooling system, precise PCB cleaning, and the application of high-performance thermal pads with exact thickness tolerances to bridge the gap between the components and the heatsink.&lt;/p></description></item></channel></rss>