<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spot-Instance on nanta - Data Engineering</title><link>https://nanta-data.dev/en/tags/spot-instance/</link><description>Recent content in Spot-Instance on nanta - Data Engineering</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 nanta</copyright><lastBuildDate>Mon, 09 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nanta-data.dev/en/tags/spot-instance/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS EC2 Instance Architecture Comparison: ARM Graviton4 vs AMD Turin — Is the Fastest Instance the Best Choice?</title><link>https://nanta-data.dev/en/posts/ec2-instance-architecture-comparison/</link><pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate><guid>https://nanta-data.dev/en/posts/ec2-instance-architecture-comparison/</guid><description>In the 2026 cloud VM benchmarks, AMD EPYC Turin (C8a) dominated both single-threaded and multi-threaded performance. Should we migrate our Graviton (ARM) data platform infrastructure to C8a? After analyzing the vCPU vs physical core distinction, Spot price-to-core efficiency, and workload characteristics — the conclusion is that a hybrid strategy beats a full migration.</description></item><item><title>Flink on EKS In-place Scaling: Scaling TaskManagers Without Restarting the Job</title><link>https://nanta-data.dev/en/posts/flink-in-place-scaling/</link><pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate><guid>https://nanta-data.dev/en/posts/flink-in-place-scaling/</guid><description>Our recommendation system&amp;rsquo;s Flink application required sub-1-minute latency, which prevented us from using autoscaling or spot instances. Autoscaling or spot reclamation triggered full Flink restarts that took 2-3 minutes. Using Flink 1.18&amp;rsquo;s adaptive scheduler and K8s Operator 1.8, we enabled in-place scaling — reducing consumer lag peaks to 1/5 and lag duration from 5-7 minutes to 2-3 minutes during scale events.</description></item></channel></rss>