<?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>Proactive_reclamation on DAMON Project Website</title>
    <link>https://damonitor.github.io/tags/proactive_reclamation/</link>
    <description>Recent content in Proactive_reclamation on DAMON Project Website</description>
    <image>
      <title>DAMON Project Website</title>
      <url>https://damonitor.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://damonitor.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.131.0</generator>
    <language>en</language>
    <lastBuildDate>Sun, 22 Nov 2026 12:31:00 -0700</lastBuildDate>
    <atom:link href="https://damonitor.github.io/tags/proactive_reclamation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Wrong example command for auto-tuned DAMON-based proactive reclamation, and solution/workarounds</title>
      <link>https://damonitor.github.io/posts/wrong_damon_reclaim_command/</link>
      <pubDate>Sun, 22 Nov 2026 12:31:00 -0700</pubDate>
      <guid>https://damonitor.github.io/posts/wrong_damon_reclaim_command/</guid>
      <description>This is also posted to the mailing list.
Hello community,
I suggested wrong way to utilize DAMON for auto-tuned proactive reclamation. Let me explain more details and correct way to do that.
Wrong Suggestion In OSSummit Europe&#39;26 and a few offline discussions, I suggested [1,2,3] people to try DAMON-based auto-tuned based proactive reclamation using DAMON user-space tool (damo) [4] like below:
$ sudo ./damo start --monitoring_intervals_autotune \ --damos_action pageout --damos_access_rate 0% 0% \ --damos_age 2m max \ --damos_quota_space 128M --damos_quota_interval 1s \ --damos_quota_goal some_mem_psi_us 5000 I found [5] it will reclaim much less than expected amount of memory.</description>
    </item>
  </channel>
</rss>
