惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - 三生石上(FineUI控件)
博客园 - Franky
GbyAI
GbyAI
B
Blog
WordPress大学
WordPress大学
D
Docker
小众软件
小众软件
月光博客
月光博客
博客园 - 【当耐特】
T
The Blog of Author Tim Ferriss
IT之家
IT之家
腾讯CDC
Engineering at Meta
Engineering at Meta
Vercel News
Vercel News
H
Help Net Security
M
MIT News - Artificial intelligence
L
LangChain Blog
云风的 BLOG
云风的 BLOG
S
SegmentFault 最新的问题
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
美团技术团队
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
V
V2EX
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How We Made Ktor JSON Parsing 66% Faster with 50% Less Me...
Juan Hurtado · 2026-06-25 · via DEV Community
Cover image for How We Made Ktor JSON Parsing 66% Faster with 50% Less Memory on KMP

Juan Hurtado

If you are building Kotlin Multiplatform applications, you know that JSON serialization is often one of the main bottlenecks in high-throughput backends and mobile apps—especially regarding CPU cycles and Garbage Collector (GC) pressure.

I’ve been working on Ghost Serializer—a byte-first JSON serializer designed for KMP, and the official HTTP Arena benchmarks just went live showing some wild improvements when integrated with Ktor.


📊 The Proof (HTTP Arena Benchmarks)

Don't take my word for it. Here is the raw comparison of Ktor base vs. Ktor + Ghost under load:

  • JSON Throughput: Slashed latency to jump from 395k to 658k rps (+66.6% speedup).
  • Heap Memory Consumption: Plunged from 9.90 GiB to 4.80 GiB (Over 50% memory reduction).
  • High-Load Complex APIs (API-16): Throughput rose by +22.2% while slashing memory by 35% (from 2.00 GiB down to 1.30 GiB).

🤝 Zero-Risk: Full Coexistence with your current Serializer

You don't need to rewrite your entire project. Ghost can coexist seamlessly with your existing setup (like kotlinx.serialization, Jackson, or Gson).

If Ghost doesn't find its @GhostSerializable annotation on a class, it will return null and let Ktor fallback to your standard serializer. This means you can adopt Ghost incrementally, using it only on your highest-traffic endpoints!

How to set up coexistence in Ktor:

import io.ktor.serialization.kotlinx.json.*
import io.ktor.server.application.*
import io.ktor.server.plugins.contentnegotiation.*
import com.ghost.serialization.ktor.ghost
import kotlinx.serialization.json.Json

fun Application.module() {
    install(ContentNegotiation) {
        // 1. Ghost handles high-performance @GhostSerializable endpoints
        ghost() 
        // 2. Kotlinx.serialization (or Jackson/Gson) handles the rest as fallback
        json(Json { ignoreUnknownKeys = true })
    }
}

How to define your models:

// Processed by GHOST (High Performance)
@GhostSerializable
data class HighTrafficUser(val id: Long, val email: String)

// Processed by Kotlinx.serialization (Standard fallback)
@Serializable
data class StandardSettings(val theme: String, val enabled: Boolean)


What makes Ghost actually different?

Unlike standard serializers that parse raw buffers into intermediate strings/chars and perform standard string matching, Ghost operates at the byte/bit level:

  • Compile-time Perfect Hash Finder (No String Comparison): During compilation (via KSP2), Ghost's PerfectHashFinder searches for a collision-free multiplier and shift parameter for your class's fields. At runtime, the parser packs the first 4 bytes of the incoming JSON key into a 32-bit integer key and resolves the field index in O(1) with a simple arithmetic instruction:

val hash = ((key * multiplier + size) shr shift) and 1023

It accesses a precalculated dispatch table using this hash, matching fields instantly with zero string allocations, zero string equality checks, and zero loops.

  • Single CPU Instruction Required-Fields Check: Instead of tracking lists, arrays, or maps of parsed fields, Ghost maps them to a single Long bitmask. Validating that all required fields are present compiles down to a single bitwise CPU register check.

  • Byte-First Pipelines: It works directly on raw source bytes (ByteArray / Okio / ByteReadChannel). It avoids decoding JSON structures to string representations in the hot path, only decoding final string values when strictly requested.

  • Thread-Local Reader/Writer Pools: Keeps GC allocation pressure at absolute zero in steady-state operation by reusing pre-allocated pools.


🚀 Help us build a community!

Ghost is open-source and ready for Kotlin Multiplatform (JVM, Android, iOS, and native targets). We are looking for collaborators, feedback, and contributors to push KMP performance to its absolute limits.

If you like the project, please drop a ⭐ Star on GitHub! It helps us gain visibility, grow the community, and keep the engine running.

Let me know what you think or if you want to try it out!