<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: nicoinstrument</title><link>https://news.ycombinator.com/user?id=nicoinstrument</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 03 Jul 2026 07:59:29 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=nicoinstrument" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by nicoinstrument in "Ask HN: What are you working on? (May 2026)"]]></title><description><![CDATA[
<p>Thanks for the suggestion! Have you found that Ray Serve’s built-in autoscaling plays nicely with custom SLO-based concurrency limits, or do you usually let Ray handle the load balancing entirely?"</p>
]]></description><pubDate>Tue, 12 May 2026 05:10:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=48104424</link><dc:creator>nicoinstrument</dc:creator><comments>https://news.ycombinator.com/item?id=48104424</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48104424</guid></item><item><title><![CDATA[New comment by nicoinstrument in "Ask HN: What are you working on? (May 2026)"]]></title><description><![CDATA[
<p>I'm learning about inference by running vLLM on a k8s cluster (EKS), building a gateway to keep a <2s TTFT SLO.<p>Most recent ha-ha moment: I kept wondering if it was normal that my cluster was only able to process 4 requests per second per vLLM engine (just seemed really low to me).<p>I realized a better metric is in-flight requests... Each engine is processing 70 requests at any given time, streaming tokens for over 30s.<p>Code: <a href="https://github.com/Nicolas-Richard/vllm-on-eks" rel="nofollow">https://github.com/Nicolas-Richard/vllm-on-eks</a></p>
]]></description><pubDate>Sun, 10 May 2026 19:02:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=48086775</link><dc:creator>nicoinstrument</dc:creator><comments>https://news.ycombinator.com/item?id=48086775</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48086775</guid></item><item><title><![CDATA[New comment by nicoinstrument in "Ask HN: Who is hiring? (October 2025)"]]></title><description><![CDATA[
<p>Chime | Software Engineer, Infrastructure | Full Time | REMOTE (US)<p>We’re looking for talented engineers who:
 • Have hands-on experience in infrastructure or platform engineering.
 • Enjoy working on distributed systems, scaling, automation, and reliability.
 • Bring a passion for operational excellence and continual improvement.
 • If this sounds like you, check out the position here: <a href="https://lnkd.in/gxz2Kac8">https://lnkd.in/gxz2Kac8</a></p>
]]></description><pubDate>Thu, 02 Oct 2025 19:55:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=45454700</link><dc:creator>nicoinstrument</dc:creator><comments>https://news.ycombinator.com/item?id=45454700</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45454700</guid></item><item><title><![CDATA[New comment by nicoinstrument in "We preview Kubernetes changes at Chime"]]></title><description><![CDATA[
<p>Thank you! 
1. I think it can be compared to a process of rendering the charts on your local machine to preview the changes and possibly pasting them in your PR for the reviewer. Sort of like mani-diffy by fully manual, yuck.
2. The other obvious comparison is with a process where diffs are reviewed in the ArgoCD web UI, assuming you have all your ArgoCD apps in "autosync: no" mode. This would be  after the PR is merged, thus fracturing the review experience, not ideal. It would also cripple ArgoCD a little as the autosync feature is very key to the experience.</p>
]]></description><pubDate>Tue, 19 Dec 2023 01:25:12 +0000</pubDate><link>https://news.ycombinator.com/item?id=38690659</link><dc:creator>nicoinstrument</dc:creator><comments>https://news.ycombinator.com/item?id=38690659</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38690659</guid></item><item><title><![CDATA[New comment by nicoinstrument in "Punjabi Mexican Americans"]]></title><description><![CDATA[
<p>you can watch it full length (~1hr) with a San Francisco library account : 
<a href="https://sfpl.bibliocommons.com/v2/record/S93C4825237" rel="nofollow noreferrer">https://sfpl.bibliocommons.com/v2/record/S93C4825237</a></p>
]]></description><pubDate>Thu, 07 Sep 2023 18:50:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=37423768</link><dc:creator>nicoinstrument</dc:creator><comments>https://news.ycombinator.com/item?id=37423768</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37423768</guid></item></channel></rss>