<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Embeddings on NoRaincheck</title><link>https://noraincheck.github.io/tags/embeddings/</link><description>Recent content in Embeddings on NoRaincheck</description><generator>Hugo</generator><language>en-US</language><copyright>NoRaincheck</copyright><lastBuildDate>Fri, 01 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://noraincheck.github.io/tags/embeddings/index.xml" rel="self" type="application/rss+xml"/><item><title>Embedding Alignment</title><link>https://noraincheck.github.io/posts/embedding-alignment/</link><pubDate>Fri, 01 Aug 2025 00:00:00 +0000</pubDate><guid>https://noraincheck.github.io/posts/embedding-alignment/</guid><description>&lt;h2 id="embedding-alignment"&gt;Embedding Alignment&lt;/h2&gt;&#10;&lt;p&gt;&lt;em&gt;August 2025&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Why?&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;Given the increasing use of vendored vector store solutions and dependencies on&#10;AI for mission critical systems, it is important to determine ways to ensure&#10;systems stay reliable when third party APIs degrade. Embedding alignment can be&#10;an approach to re-map embeddings from one vendored system to another in the hope&#10;that systems stay reliable at the cost of minimal degradation at inference time.&#10;This approach requires only maintaining a linear mapping between embeddings&#10;rather than duplicating vector stores for multiple vendors which can be&#10;expensive in terms of ownership, processes and infrastructure.&lt;/p&gt;</description></item><item><title>LLMs - in Review (2024)</title><link>https://noraincheck.github.io/posts/llms-in-review-2024/</link><pubDate>Sun, 01 Dec 2024 00:00:00 +0000</pubDate><guid>https://noraincheck.github.io/posts/llms-in-review-2024/</guid><description>&lt;h2 id="llms---in-review-2024"&gt;LLMs - in Review (2024)&lt;/h2&gt;&#10;&lt;p&gt;&lt;em&gt;December 2024&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;2024 was the first year where I took LLMs seriously. I successfully hosted a&#10;Llama 70b parameter model in production which was used as with&#10;&lt;a href="https://www.continue.dev/"&gt;continue.dev&lt;/a&gt; for a self-hosted co-pilot&#10;replacement, along with a code autocomplete like&#10;&lt;a href="https://qwenlm.github.io/blog/qwen2.5-coder-family/"&gt;Qwen Coder&lt;/a&gt; or&#10;&lt;a href="https://deepseekcoder.github.io/"&gt;Deepseek&lt;/a&gt;, these were fine replacements and&#10;surprisingly robust.&#10;&lt;a href="https://huggingface.co/docs/text-generation-inference/index"&gt;Huggingface&amp;rsquo;s TGI&lt;/a&gt;&#10;along with &lt;a href="https://github.com/triton-inference-server/server"&gt;Triton Server&lt;/a&gt;&#10;were the main heroes for this project, (Triton was used to serve &lt;code&gt;onnx&lt;/code&gt; models&#10;for embeddings) though I&amp;rsquo;ve yet to find a &amp;ldquo;good&amp;rdquo; embedding model. At this stage&#10;in time, most of the vector database solutions &amp;ldquo;feel&amp;rdquo; the same and can all&#10;seemingly be trivially hosted via Kubernetes.&lt;/p&gt;</description></item></channel></rss>