<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Threading on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/threading/</link>
    <description>Recent content in Threading on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Nov 2016 10:22:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/threading/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Threading Models in Java: Which One Does Your System Actually Need?</title>
      <link>https://blog.turboawesome.win/2016/11/threading-models-in-java-which-one-does-your-system-actually-need/</link>
      <pubDate>Wed, 09 Nov 2016 10:22:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2016/11/threading-models-in-java-which-one-does-your-system-actually-need/</guid>
      <description>Thread-per-request, event-loop, work-stealing, single-threaded with message passing — Java supports all of them, but each optimises for different things. Choosing the wrong model means fighting the runtime rather than working with it.</description>
    </item>
    <item>
      <title>Busy Spinning vs Blocking: Thread Strategies for Ultra-Low Latency</title>
      <link>https://blog.turboawesome.win/2014/05/busy-spinning-vs-blocking-thread-strategies-for-ultra-low-latency/</link>
      <pubDate>Wed, 14 May 2014 10:31:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2014/05/busy-spinning-vs-blocking-thread-strategies-for-ultra-low-latency/</guid>
      <description>Blocking a thread hands control to the OS scheduler and costs you microseconds on wake-up. Busy spinning wastes a CPU core. The right choice depends on your latency target and hardware budget.</description>
    </item>
  </channel>
</rss>
