<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GRPC on jdcsen</title><link>https://jdcsen.com/tags/grpc/</link><description>Recent content in GRPC on jdcsen</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 01 Jan 1970 00:33:45 +0000</lastBuildDate><atom:link href="https://jdcsen.com/tags/grpc/index.xml" rel="self" type="application/rss+xml"/><item><title>Paralinguistic Signals from a Speech LLM</title><link>https://jdcsen.com/projects/paralinguistic-features/</link><pubDate>Thu, 01 Jan 1970 00:33:45 +0000</pubDate><guid>https://jdcsen.com/projects/paralinguistic-features/</guid><description>&lt;ul&gt;&#10;&lt;li&gt;NVIDIA Triton Python backend fronting a vLLM-served speech LLM, taken from prototype to production.&lt;/li&gt;&#10;&lt;li&gt;Derives confidence, sentiment and spoken-language ID from the model&amp;rsquo;s own token-level outputs. No additional models to train or serve.&lt;/li&gt;&#10;&lt;li&gt;Orchestrates per-signal LLM queries over gRPC alongside ONNX Runtime inference for confidence calibration and forced alignment.&lt;/li&gt;&#10;&lt;li&gt;p50 latency of approximately 5 to 10 ms per signal.&lt;/li&gt;&#10;&lt;li&gt;Technical lead for a three-engineer team. A later &lt;a href="https://jdcsen.com/projects/triton-throughput-refactor/"&gt;concurrency refactor&lt;/a&gt; took sustained throughput from roughly 8 to 80 requests per second.&lt;/li&gt;&#10;&lt;/ul&gt;</description></item><item><title>gRPC Bidirectional Streaming for a C++ Node-Graph Framework</title><link>https://jdcsen.com/projects/grpc-pipe-wrapper/</link><pubDate>Thu, 01 Jan 1970 00:33:44 +0000</pubDate><guid>https://jdcsen.com/projects/grpc-pipe-wrapper/</guid><description>&lt;ul&gt;&#10;&lt;li&gt;Nova Sonic needed the speech framework&amp;rsquo;s pipelines delivered as a containerized gRPC service: audio and system prompts streaming in, inference requests streaming out. The team&amp;rsquo;s code had only ever been called through JNI.&lt;/li&gt;&#10;&lt;li&gt;Mapped gRPC C++&amp;rsquo;s bidirectional-streaming reactor onto the framework&amp;rsquo;s pipe abstraction once, as a reusable layer covering session setup and teardown, signal handling, graceful error handling and logging.&lt;/li&gt;&#10;&lt;li&gt;A new service needs under 300 lines of integration code: which pipe input receives request messages, and which pipe outputs become response messages. Adopted org-wide as the standard way to deploy a pipeline.&lt;/li&gt;&#10;&lt;li&gt;Established Protobuf and gRPC generated code as first-class CMake libraries in the framework&amp;rsquo;s build, so the same generated types are consumed by the pipeline&amp;rsquo;s nodes and by the server without duplicate-symbol conflicts.&lt;/li&gt;&#10;&lt;/ul&gt;</description></item></channel></rss>