<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Stevens Blog</title>
    <link>https://dsmike.de/en/posts/</link>
    <description>Recent content in Posts on Stevens Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 15 Jan 2026 18:37:32 +0100</lastBuildDate>
    <atom:link href="https://dsmike.de/en/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RTX 3090 vs RTX PRO 4000 (Blackwell): Inference, Training, and Power Cost</title>
      <link>https://dsmike.de/en/posts/ai/compare_gpus/</link>
      <pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://dsmike.de/en/posts/ai/compare_gpus/</guid>
      <description>&lt;p&gt;I wanted to know how my local RTX 3090 (used, ~€700) compares to one or more RTX PRO 4000 Blackwell cards (145W, new ~€1400) for both LLM inference (single user / scripts / my own agents) and fine-tuning image models (AI-toolkit).&lt;/p&gt;&#xA;&lt;p&gt;My takeaway up front: with llama.cpp the 3090 is often faster at decoding; for training the RTX PRO 4000 is slightly ahead for me. In terms of power cost per token/epoch the RTX PRO 4000 is much nicer.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Docker in a dedicated VLAN including IPv6</title>
      <link>https://dsmike.de/en/posts/linux/docker_macvlan/</link>
      <pubDate>Sun, 17 Dec 2023 00:00:00 +0000</pubDate>
      <guid>https://dsmike.de/en/posts/linux/docker_macvlan/</guid>
      <description>&lt;p&gt;To test AdGuard Home I wanted to quickly spin up a Docker container. That worked right away, but it didn’t correctly log the clients’ IPv6 addresses. The solution was to place the container on the network as its own host.&lt;/p&gt;&#xA;&lt;h2 id=&#34;step-1-create-a-vlan-on-unifi-udmpro&#34;&gt;Step 1: Create a VLAN on UniFi UDM‑Pro&lt;/h2&gt;&#xA;&lt;p&gt;Because containers with macvlan don’t properly use DHCP, I created a VLAN with its own IP range. In the UDM‑Pro web UI go to “Settings” → “Network” → “New Virtual Network”. Assign an IP range and a VLAN ID (I used ID 2). Set DHCP to None. Under IPv6, also assign a subnet, for example &lt;code&gt;fd01::1/64&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pulse counter</title>
      <link>https://dsmike.de/en/posts/iot/pulse_counter/</link>
      <pubDate>Thu, 05 Jan 2023 21:35:17 +0100</pubDate>
      <guid>https://dsmike.de/en/posts/iot/pulse_counter/</guid>
      <description>&lt;p&gt;To simplify the reading and evaluation of my electricity meter, I have built a reading head using an ESP32 board and a TRCT5000 infrared sensor. Unfortunately, I still have an old, so-called &amp;ldquo;Ferraries electricity meter&amp;rdquo;. But this one has a turntable with a red mark. This makes X revolutions per kWh, in my case 75. By the duration of a revolution the momentary consumption can be calculated then.&lt;/p&gt;&#xA;&lt;p&gt;For the sensor, I then 3D printed a housing to mount it on the meter and align it. To fix the sensor, I used adhesive tape, which is normally used to mask walls when painting, in order to get sharp edges. This tape can be removed easily and still sticks sufficiently. I designed the case in Autodesk Fusion 360.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ERCF Speedboard</title>
      <link>https://dsmike.de/en/posts/pcb/ercf_speedboard/</link>
      <pubDate>Fri, 30 Dec 2022 00:00:00 +0000</pubDate>
      <guid>https://dsmike.de/en/posts/pcb/ercf_speedboard/</guid>
      <description>&lt;h2 id=&#34;why-all-this&#34;&gt;Why all this?&lt;/h2&gt;&#xA;&lt;p&gt;The ERCF Speedboard is my first self-made board for my 3D printer.&lt;/p&gt;&#xA;&lt;p&gt;I was motivated by the ERCF Easy Board ( &lt;a href=&#34;https://github.com/Tircown/ERCF-easy-brd&#34;&gt;https://github.com/Tircown/ERCF-easy-brd&lt;/a&gt; ). In the 3D printer itself (a Voron 2.4) I used the&#xA;mainboard is the Fysetc Spider v1.1, which I recently changed from Klipper to RepRap firmware. There was no particular reason for this, I just wanted to try it out. However, I have lost the ability to communicate with the ERCF Easy Brd as a result. Of course, this is a pity, but also a new challenge.&lt;/p&gt;</description>
    </item>
    <item>
      <title>JVC Autocal</title>
      <link>https://dsmike.de/en/posts/heimkino/autocal/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://dsmike.de/en/posts/heimkino/autocal/</guid>
      <description>&lt;p&gt;To calibrate the JVC X5000 projector, there is a software from JVC called Autocal.&#xA;Unfortunately this does not work together with the colorimeter i1Display Pro.&#xA;But there is another software project ArgyllCMS which can use the sensor.&#xA;So I thought some time ago, why not write a wrapper that connects&#xA;the open source software with the software from JVC. The result is a DLL file,&#xA;which pretends to be a Spyder colorimeter, but calls the ArgyllCMS in the background.&#xA;So you can simply replace the Spyder DLL in the Autocal software and then instead of the&#xA;Spyder sensor the framework is used, which can then use the i1Display Pro.&#xA;The whole thing at least works reliably enough to calibrate my projector and&#xA;a few other people have already used it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
