# json lines format

JSON Lines is a newline-delimited JSON text format for storing structured data one record per line.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Inside Agentwhy, Part 1: A Step-by-Step Audit Trail for AI Coding Agents

DevFeed: [Inside Agentwhy, Part 1: A Step-by-Step Audit Trail for AI Coding Agents](<https://devfeed.tech/articles/inside-agentwhy-part-1-a-step-by-step-audit-trail-for-ai-coding-agents-142899.md>)

Original publisher: [Read original article](<https://hackernoon.com/inside-agentwhy-part-1-a-step-by-step-audit-trail-for-ai-coding-agents?source=rss>)

Author: Karol

Published: 2026-11-19T08:32:55Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [audit](<https://devfeed.tech/topics/audit.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [json lines format](<https://devfeed.tech/topics/json-lines-format.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent-audit](<https://devfeed.tech/tags/ai-agent-audit.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-code-jsonl](<https://devfeed.tech/tags/claude-code-jsonl.md>), [coding](<https://devfeed.tech/tags/coding.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [delegation](<https://devfeed.tech/tags/delegation.md>), [demo](<https://devfeed.tech/tags/demo.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [sha-256-fingerprints](<https://devfeed.tech/tags/sha-256-fingerprints.md>)

### AI overview

agentwhy turns saved coding-agent conversations into an ordered audit trail showing reads, commands, changes, blocked attempts, and helper handoffs with each helper's task and model. For Claude Code, it matches helper files to Agent calls by call ID; ambiguous or missing links are marked unresolved rather than guessed, since timestamps can be unreliable. It also checks command output against salted hashes of distinctive lines from private project files to detect reads that omit filenames. This can add evidence of a read but does not remove one, and has limits: it excludes files outside the project, skips large files or projects beyond stated thresholds, and misses partial, transformed, or changed content. The excerpt says Codex and Copilot reports are less complete, and MCP tools' file access is not visible. agentwhy runs locally; the post says secret values are replaced before the page is built.

### Source excerpt

One part of agentwhy each week. This one shows every step your AI and its helpers took, and where a rule stopped them.

## jXBW: A Compressed Index Enabling Structure-Aware JSONL Retrieval for Structured RAG

DevFeed: [jXBW: A Compressed Index Enabling Structure-Aware JSONL Retrieval for Structured RAG](<https://devfeed.tech/articles/jxbw-a-compressed-index-enabling-structure-aware-jsonl-retrieval-for-structured-rag-138277.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2508.12536>)

Author: Yasuo Tabei

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>)

Topics: [json lines format](<https://devfeed.tech/topics/json-lines-format.md>), [Vectors & LLMs](<https://devfeed.tech/topics/vectors-llms.md>), [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [cs-db](<https://devfeed.tech/tags/cs-db.md>), [cs-ds](<https://devfeed.tech/tags/cs-ds.md>), [cs-ir](<https://devfeed.tech/tags/cs-ir.md>), [encoding](<https://devfeed.tech/tags/encoding.md>), [geospatial](<https://devfeed.tech/tags/geospatial.md>), [index](<https://devfeed.tech/tags/index.md>), [json](<https://devfeed.tech/tags/json.md>), [language-models](<https://devfeed.tech/tags/language-models.md>), [large-language-models-llms](<https://devfeed.tech/tags/large-language-models-llms.md>), [llm-prompts](<https://devfeed.tech/tags/llm-prompts.md>), [llms](<https://devfeed.tech/tags/llms.md>), [openstreetmap](<https://devfeed.tech/tags/openstreetmap.md>), [pubchem](<https://devfeed.tech/tags/pubchem.md>), [query](<https://devfeed.tech/tags/query.md>), [rag](<https://devfeed.tech/tags/rag.md>), [reasoning](<https://devfeed.tech/tags/reasoning.md>), [retrieval](<https://devfeed.tech/tags/retrieval.md>), [retrieval-augmented-generation](<https://devfeed.tech/tags/retrieval-augmented-generation.md>), [retrieval-augmented-generation-rag](<https://devfeed.tech/tags/retrieval-augmented-generation-rag.md>), [structure](<https://devfeed.tech/tags/structure.md>), [structured](<https://devfeed.tech/tags/structured.md>)

### AI overview

jXBW enables direct substructure search over JSONL collections using a compressed index, avoiding the per-query structure reconstruction used by recent RAG systems. It merges repeated tree structures across objects, encodes them with the eXtended Burrows-Wheeler Transform (XBW), and searches in three phases. The authors say query cost depends on candidate matches and results rather than requiring a full collection scan. Across seven real-world datasets, including PubChem (1 million compounds) and OpenStreetMap (6.6 million objects), jXBW reportedly beat the strongest tree-based baseline by 16x on the smallest dataset and up to 2,800x on the largest. Saxon did not finish 1,000 PubChem queries within 24 hours; jXBW searches over million-object JSONL collections were reported in the sub-millisecond range.

### Source excerpt

arXiv:2508.12536v5 Announce Type: replace Abstract: Providing structured information to large language models (LLMs) has been shown to improve multi-step reasoning and factual accuracy (e.g., StructRAG, ICLR 2025; RAS, ICLR 2026); recent retrieval-augmented generation (RAG) systems reconstruct structure from retrieved text on every query. When the corpus is already structured, as in JSON Lines (JSONL), used for LLM prompts, chemical compounds, and geospatial objects, this per-query rebuilding can be replaced by direct structural retrieval. Its core operation is substructure search: finding all JSON objects in a collection that contain a given query tree. Existing approaches index each object separately, so index space and query time grow with collection size; XML-based engines add conversion overhead and semantic mismatches. We propose jXBW, a compressed index for fast substructure search over JSONL, combining three innovations: (i) a merged tree representation that consolidates repeated structures across objects, (ii) a succinct tree encoding based on the eXtended Burrows-Wheeler Transform (XBW), and (iii) a three-phase substructure search algorithm on this encoding. Together they achieve query-dependent complexity in compressed space: the search avoids a full scan of the collection, and its cost grows with the numbers of candidate matches and results. Experiments on seven real-world datasets, including PubChem (1 million compounds) and OpenStreetMap (6.6 million objects), show that jXBW outperforms the strongest tree-based baseline by 16x on the smallest dataset and by up to 2,800x on the largest, while the XML-based engine Saxon does not complete the 1,000-query workload on PubChem within 24 hours. jXBW brings substructure search over million-object JSONL collections into the sub-millisecond range.

## Reading JSON at 277 GB/s in Python

DevFeed: [Reading JSON at 277 GB/s in Python](<https://devfeed.tech/articles/reading-json-at-277-gb-s-in-python-134077.md>)

Original publisher: [Read original article](<https://lemire.me/blog/2026/11/14/reading-json-at-277-gb-s-in-python/>)

Author: Daniel Lemire

Published: 2026-11-14T14:53:50Z

Content type: article

Language: en

Sources: [Daniel Lemire](<https://devfeed.tech/sources/daniel-lemire.md>)

Topics: [json lines format](<https://devfeed.tech/topics/json-lines-format.md>), [Python](<https://devfeed.tech/topics/python.md>), [JSON](<https://devfeed.tech/topics/json.md>)

Tags: [json](<https://devfeed.tech/tags/json.md>), [python](<https://devfeed.tech/tags/python.md>), [reading](<https://devfeed.tech/tags/reading.md>)

### AI overview

In the reported benchmarks, fastsimdjson combines selective field extraction with threaded parsing to reach 138 GB/s when counting GitHub stars across 7.6 GB of NDJSON on a 192-core AWS instance; extracting fields from a Twitter benchmark file reaches 277 GB/s. On the counting task, it outpaces the best msgspec process pool (116 GB/s at 96 processes), with the advantage narrowing from 3.5x on one core to about 20% at scale. Across six benchmark files, four exceed 100 GB/s, while one is near 20 GB/s and another ties msgspec. The article notes counting is especially favorable to processes because little data must be returned.

### Source excerpt

Many systems log their data as JSON, one record per line (NDJSON). GitHub, for example, publishes every public event on its site that way through GH Archive: about a gigabyte per hour. Suppose you want to know which repositories received the most stars over eight hours. That is 7.6 GB of JSON, 2.2 million events. ... Continue reading Reading JSON at 277 GB/s in Python

## Parsing JSON at tens of gigabytes per second... in Python

DevFeed: [Parsing JSON at tens of gigabytes per second... in Python](<https://devfeed.tech/articles/parsing-json-at-tens-of-gigabytes-per-second-in-python-85593.md>)

Original publisher: [Read original article](<https://lemire.me/blog/2026/10/12/parsing-json-at-tens-of-gigabytes-per-second-in-python/>)

Author: Daniel Lemire

Published: 2026-10-12T13:06:39Z

Content type: article

Language: en

Sources: [Daniel Lemire](<https://devfeed.tech/sources/daniel-lemire.md>)

Topics: [JSON](<https://devfeed.tech/topics/json.md>), [json lines format](<https://devfeed.tech/topics/json-lines-format.md>), [Python](<https://devfeed.tech/topics/python.md>), [Scapy](<https://devfeed.tech/topics/scapy.md>), [Numba](<https://devfeed.tech/topics/numba.md>)

Tags: [json](<https://devfeed.tech/tags/json.md>), [parallelism](<https://devfeed.tech/tags/parallelism.md>), [python](<https://devfeed.tech/tags/python.md>), [python-3-14](<https://devfeed.tech/tags/python-3-14.md>), [thread](<https://devfeed.tech/tags/thread.md>)

### AI overview

The article benchmarks parsing 7.6 GB of GitHub event data with Python 3.14's free-threaded build. Using fastsimdjson with lazy views and 64 threads, it processes the data in about 0.12 seconds, or 66 GB/s, and compares the result with other JSON parsers.

### Source excerpt

Python used to have limited parallelism, due to its global interpreter lock (GIL). Only one thread could run Python code at a time. Python 3.14 comes in a free-threaded version (python3.14t), without the global interpreter lock. Several threads can now run Python code at the same time. Let us pick a realistic problem. GitHub publishes ... Continue reading Parsing JSON at tens of gigabytes per second... in Python

## ★ Streaming AI replies from Laravel to React

DevFeed: [★ Streaming AI replies from Laravel to React](<https://devfeed.tech/articles/streaming-ai-replies-from-laravel-to-react-65084.md>)

Original publisher: [Read original article](<https://freek.dev/3092-streaming-ai-replies-from-laravel-to-react>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-05T10:30:47Z

Content type: tutorial

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [React](<https://devfeed.tech/topics/react.md>), [json lines format](<https://devfeed.tech/topics/json-lines-format.md>), [vercel ai sdk](<https://devfeed.tech/topics/vercel-ai-sdk.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [Real-time AI interactions](<https://devfeed.tech/topics/real-time-ai-interactions.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-sdk](<https://devfeed.tech/tags/ai-sdk.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [cache](<https://devfeed.tech/tags/cache.md>), [helpdesk](<https://devfeed.tech/tags/helpdesk.md>), [json](<https://devfeed.tech/tags/json.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [llm](<https://devfeed.tech/tags/llm.md>), [react](<https://devfeed.tech/tags/react.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [replies](<https://devfeed.tech/tags/replies.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [stream](<https://devfeed.tech/tags/stream.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [string](<https://devfeed.tech/tags/string.md>)

### AI overview

A tutorial shows how a Laravel service streams AI chat replies and tool-call events to a React frontend using newline-delimited JSON. It explains buffering partial lines in the browser, updating the chat interface as events arrive, and saving the completed assistant message.

### Source excerpt

A couple of posts back I walked through the agent and tools we built on top of the Laravel AI SDK for There There, the helpdesk we're putting together at Spatie. I ended that post on a small cliffhanger. We hand the agent off to a streaming service that turns the SDK's response stream into events the frontend can consume. That's this post. A quick reminder on our angle. After two decades of running our own customer support, we wanted a helpdesk where AI makes support agents faster, not one that tries to replace them. The human reads, thinks, and directs. The model drafts and retrieves in real time while they watch. There There is in private beta right now, and you can apply for early access at there-there.app. Streaming from Laravel to React The obvious way to hand an LLM response to the browser is to wait for it to finish, then render the whole thing. That's easy, but it makes the agent feel sluggish. What we actually want is for the reply to appear word by word, and for the agent's own reasoning (like which tool it's calling) to be narrated along the way. The Laravel AI SDK exposes each step of a conversation as a typed event. We iterate over that stream and emit newline-delimited JSON for the frontend, one line per event. Here's the core of our AgentStreamingService. public function stream(Agent&HasTools $agent, string $message, AgentChat $chat): StreamedResponse { return response()->stream(function () use ($agent, $message, $chat): Generator { yield from $this->streamAgent($agent, $message, $chat); }, 200, [ 'Content-Type' => 'application/x-ndjson', 'Cache-Control' => 'no-cache', ]); } private function streamAgent(Agent&HasTools $agent, string $message, AgentChat $chat): Generator { set_time_limit(120); $fullContent = ''; $toolCalls = []; foreach ($agent->stream($message) as $event) { if ($event instanceof ToolCall) { yield json_encode(['type' => 'tool_call', 'tool_name' => $event->toolCall->name])."\n"; } if ($event instanceof TextDelta) { $fullContent .= $even

## Scalable JSON Streaming with HTTP and Go - Ep.5

DevFeed: [Scalable JSON Streaming with HTTP and Go - Ep.5](<https://devfeed.tech/articles/scalable-json-streaming-with-http-and-go-ep-5-22271.md>)

Original publisher: [Read original article](<https://www.ardanlabs.com/blog/2024/11/scalable-json-streaming-with--http-and-go.html>)

Published: 2024-11-25T00:00:00Z

Content type: tutorial

Language: en

Sources: [William Kennedy](<https://devfeed.tech/sources/william-kennedy.md>)

Topics: [Streaming](<https://devfeed.tech/topics/streaming.md>), [encoding/json](<https://devfeed.tech/topics/encoding-json.md>), [json lines format](<https://devfeed.tech/topics/json-lines-format.md>), [JSON](<https://devfeed.tech/topics/json.md>), [dataset](<https://devfeed.tech/topics/dataset.md>), [Error Handling](<https://devfeed.tech/topics/error-handling.md>)

Tags: [advanced](<https://devfeed.tech/tags/advanced.md>), [chunked-transfer-json](<https://devfeed.tech/tags/chunked-transfer-json.md>), [decoding-json-streams](<https://devfeed.tech/tags/decoding-json-streams.md>), [efficient-json-handling](<https://devfeed.tech/tags/efficient-json-handling.md>), [encoding-json](<https://devfeed.tech/tags/encoding-json.md>), [encoding-json-in-go](<https://devfeed.tech/tags/encoding-json-in-go.md>), [go](<https://devfeed.tech/tags/go.md>), [go-json-encoding](<https://devfeed.tech/tags/go-json-encoding.md>), [go-json-memory-management](<https://devfeed.tech/tags/go-json-memory-management.md>), [handling-large-json-files](<https://devfeed.tech/tags/handling-large-json-files.md>), [http](<https://devfeed.tech/tags/http.md>), [http-chunked-encoding](<https://devfeed.tech/tags/http-chunked-encoding.md>), [json](<https://devfeed.tech/tags/json.md>), [json-chunked-transfer](<https://devfeed.tech/tags/json-chunked-transfer.md>), [json-error-logging](<https://devfeed.tech/tags/json-error-logging.md>), [json-lines-format](<https://devfeed.tech/tags/json-lines-format.md>), [json-lines-ndjson](<https://devfeed.tech/tags/json-lines-ndjson.md>), [json-object](<https://devfeed.tech/tags/json-object.md>), [json-streaming](<https://devfeed.tech/tags/json-streaming.md>), [json-streaming-in-go](<https://devfeed.tech/tags/json-streaming-in-go.md>), [large-datasets](<https://devfeed.tech/tags/large-datasets.md>), [logging](<https://devfeed.tech/tags/logging.md>), [memory](<https://devfeed.tech/tags/memory.md>), [memory-efficient-data-transmission](<https://devfeed.tech/tags/memory-efficient-data-transmission.md>), [memory-efficient-json](<https://devfeed.tech/tags/memory-efficient-json.md>), [practical](<https://devfeed.tech/tags/practical.md>), [query](<https://devfeed.tech/tags/query.md>), [real-time-json-streaming](<https://devfeed.tech/tags/real-time-json-streaming.md>), [scalable-json-processing](<https://devfeed.tech/tags/scalable-json-processing.md>), [stream](<https://devfeed.tech/tags/stream.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [streaming-data](<https://devfeed.tech/tags/streaming-data.md>), [streaming-json-over-http](<https://devfeed.tech/tags/streaming-json-over-http.md>), [streaming-large-json-datasets](<https://devfeed.tech/tags/streaming-large-json-datasets.md>), [streams](<https://devfeed.tech/tags/streams.md>)

### AI overview

For large datasets, the text recommends streaming JSON Lines (NDJSON) instead of building one large JSON object in memory, sending records incrementally to reduce memory use. In Go, an encoder can write each object with a newline; decoding requires a loop that handles incoming data without memory reuse causing stale or incorrect values. Over HTTP/1.1, the response writer can be used to encode objects and flush after each one for incremental delivery. Once streaming begins, the HTTP status code cannot be changed, so the text emphasizes logging errors. It mentions Netcat demonstrations but provides no further details in the supplied excerpt.

### Source excerpt

Introduction: Welcome to the final episode of the JSON for Engineers series! In this concluding session, we tackle the challenges of working with large JSON datasets, exploring efficient strategies for streaming data while minimizing memory usage. These techniques enable developers to handle massive payloads without overburdening system resources, ensuring scalable and cost-effective applications. JSON Streaming: Using JSON Lines for memory-efficient data transmission. HTTP Chunked Encoding: Leveraging HTTP/1.1 chunked transfer encoding for streaming large datasets. Practical Error Handling: Logging and managing errors in streaming JSON responses. This episode starts by addressing the inefficiencies of constructing large JSON objects in memory when working with massive datasets, such as database query results. Instead of consuming significant memory to create one monolithic JSON object, the recommended approach involves using JSON Lines (NDJSON), a format where each line represents a separate JSON object. This method reduces memory requirements by transmitting data incrementally. Using Go's encoding/json package, developers can easily encode and stream multiple JSON objects, as it automatically appends newlines between objects. On the receiving end, decoding JSON streams requires careful looping to handle incoming data dynamically while avoiding memory reuse issues, which could lead to errors or stale data.

## How to Load Data From JSON to BigQuery (3 Easy Methods)

DevFeed: [How to Load Data From JSON to BigQuery (3 Easy Methods)](<https://devfeed.tech/articles/how-to-load-data-from-json-to-bigquery-3-easy-methods-126851.md>)

Original publisher: [Read original article](<https://estuary.dev/blog/json-to-bigquery>)

Author: Jeffrey Richman

Published: 2023-10-24T19:57:17Z

Content type: tutorial

Language: en

Sources: [Estuary](<https://devfeed.tech/sources/estuary.md>)

Topics: [BigQuery](<https://devfeed.tech/topics/bigquery.md>), [JSON](<https://devfeed.tech/topics/json.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [json lines format](<https://devfeed.tech/topics/json-lines-format.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [automated](<https://devfeed.tech/tags/automated.md>), [bigquery](<https://devfeed.tech/tags/bigquery.md>), [easy](<https://devfeed.tech/tags/easy.md>), [export](<https://devfeed.tech/tags/export.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [json](<https://devfeed.tech/tags/json.md>), [load](<https://devfeed.tech/tags/load.md>)

### AI overview

BigQuery's bq CLI and Cloud Console load newline-delimited JSON (JSONL), so regular JSON with comma-separated objects must be reformatted. The CLI workflow uses Cloud Shell, a project and dataset, and `bq load` with a source path and schema; the Console workflow creates a dataset and table, lets users choose a source and enter or auto-detect the schema, and offers optional partition and clustering settings. The article also describes Estuary's no-code pipeline: capture JSON from an HTTP endpoint, configure BigQuery as the destination, and publish for continuous near-real-time synchronization. Manual methods must be repeated as data changes. The text notes that schema autodetection can miss nested arrays, incorrect schemas may prevent loading, and Cloud Storage object versioning is unsupported with no guaranteed consistency for external sources.

### Source excerpt

Discover efficient ways to export JSON data to BigQuery for advanced analysis and integration with diverse technologies. Learn manual and automated methods in this article.

## Redsea 0.7, a lightweight RDS decoder

DevFeed: [Redsea 0.7, a lightweight RDS decoder](<https://devfeed.tech/articles/redsea-0-7-a-lightweight-rds-decoder-21648.md>)

Original publisher: [Read original article](<https://www.windytan.com/2016/10/redsea-07-lightweight-rds-decoder.html>)

Author: Oona Räisänen (noreply@blogger.com)

Published: 2016-10-02T19:10:00Z

Content type: article

Language: en

Sources: [Oona Räisänen](<https://devfeed.tech/sources/oona-raisanen.md>)

Topics: [communications](<https://devfeed.tech/topics/communications.md>), [json lines format](<https://devfeed.tech/topics/json-lines-format.md>), [JSON](<https://devfeed.tech/topics/json.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [IO](<https://devfeed.tech/topics/io.md>)

Tags: [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [decoder](<https://devfeed.tech/tags/decoder.md>), [fm-radio](<https://devfeed.tech/tags/fm-radio.md>), [formats](<https://devfeed.tech/tags/formats.md>), [json](<https://devfeed.tech/tags/json.md>), [lightweight](<https://devfeed.tech/tags/lightweight.md>), [radio](<https://devfeed.tech/tags/radio.md>), [rds](<https://devfeed.tech/tags/rds.md>), [receiver](<https://devfeed.tech/tags/receiver.md>), [rtl](<https://devfeed.tech/tags/rtl.md>), [software](<https://devfeed.tech/tags/software.md>), [types](<https://devfeed.tech/tags/types.md>)

### AI overview

Redsea 0.7.6 decodes FM multiplex signals from an rtl-sdr receiver and rtl_fm, as well as ASCII-binary or line-by-line hex RDS input; the latter format is also used by RDS Spy. Its default output is verbose line-delimited JSON, one object per group, for machine processing, and it can also emit hex groups. The author reports that the C++ rewrite using liquid-dsp uses about 40% CPU on a Raspberry Pi 1, alongside a similar demand from rtl_fm, and 0.9% of one laptop CPU core; it is single-threaded and uses 1,500 KB of memory. The excerpt says sensitivity was improved in recent versions but may still be a problem, then cuts off before providing test results.

### Source excerpt

I've written about redsea, my RDS decoder project, many times before. It has changed a lot lately; it even has a version number, 0.7.6 as of this writing. What follows is a summary of its current state and possible future developments. Input formats Redsea can decode several types of data streams. The command-line switches to activate these can be found in the readme. Its main use, perhaps, is to demodulate an FM multiplex carrier, as received using a cheap rtl-sdr radio dongle and demodulated using rtl_fm. The multiplex is an FM demodulated signal sampled at 171 kHz, a convenient multiple of the RDS data rate (1187.5 bps) and the subcarrier frequency (57 kHz). There's a convenience shell script that starts both redsea and the rtl_fm receiver. For example, ./rtl-rx.sh -f 88.0M would start reception on 88.0 MHz. It can also decode an "ASCII binary" stream (--input-ascii): 0001100100111001000101110000101110011000010010110010011001000000100001 1010010000011010110100010000000100000001101110000100010111000010111001 1001000010110000111111011101101011001010101110100011111101000011100010 100000011010010001011100001 Or hex-encoded RDS groups one per line (--input-hex), which is the format used by RDS Spy: 6201 01D8 E704 594C 6201 01D9 2217 4520 6201 E1C1 594C 6202 6201 01DA 1139 594B 6201 21DC 2020 2020 Output formats The default output has changed drastically. There used to be no strict format to it, rather it was just a human-readable terminal display. This sort of output format will probably return at some point, as an option. But currently redsea outputs line-delimited JSON, where every group is a JSON object on a separate line. It is quite verbose but machine readable and well-suited for post-processing: {"pi":"0x6201","group":"0A","tp":false,"prog_type":"Serious classical","ta":tru e,"is_music":true,"alt_freqs":[87.9,88.5,89.2,89.5,89.8,90.9,93.2],"ps":"YLE YK SI"} {"pi":"0x6201","group":"14A","tp":false,"prog_type":"Serious classical","other_ network":{"pi":"0x6205","