<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Online Learning on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/online-learning/</link><description>Recent content in Online Learning on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 12 Jan 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/online-learning/index.xml" rel="self" type="application/rss+xml"/><item><title>Recommendation Systems (15): Real-Time Recommendation and Online Learning</title><link>https://www.chenk.top/en/recommendation-systems/15-real-time-online/</link><pubDate>Mon, 12 Jan 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/recommendation-systems/15-real-time-online/</guid><description>&lt;blockquote>
&lt;p>A user opens your app at 14:02 and searches for &amp;rsquo;trail running shoes&amp;rsquo;. By 15:30, they&amp;rsquo;ve moved on to reading kitchen reviews. A model that retrains nightly still shows them Salomon ads at 16:00 — and that gap is exactly the bug a real-time system fixes. The interesting part isn&amp;rsquo;t &amp;lsquo;make it faster&amp;rsquo; but &amp;lsquo;what &lt;em>should&lt;/em> be fast&amp;rsquo; — most features add nothing to AUC even when made real-time, and the wrong design point wastes money without improving performance.&lt;/p></description></item></channel></rss>