<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Developers Forum for XinFin XDC Network: Tom M</title>
    <description>The latest articles on Developers Forum for XinFin XDC Network by Tom M (@tm_ba4f54).</description>
    <link>https://www.xdc.dev/tm_ba4f54</link>
    <image>
      <url>https://www.xdc.dev/images/liCXIt_dLQAl_VgtrJrvuoZc-Iz3niG9ghIXbTk78T4/rs:fill:90:90/mb:500000/ar:1/aHR0cHM6Ly93d3cu/eGRjLmRldi91cGxv/YWRzL3VzZXIvcHJv/ZmlsZV9pbWFnZS8y/MzczLzIyYjZiODRi/LWNlN2UtNGZkYi04/YzVjLWU4ZDk4MTgx/ZGJmNC5wbmc</url>
      <title>Developers Forum for XinFin XDC Network: Tom M</title>
      <link>https://www.xdc.dev/tm_ba4f54</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.xdc.dev/feed/tm_ba4f54"/>
    <language>en</language>
    <item>
      <title>[WIP] debug_traceBlockByNumber way too slow</title>
      <dc:creator>Tom M</dc:creator>
      <pubDate>Tue, 12 Dec 2023 10:18:30 +0000</pubDate>
      <link>https://www.xdc.dev/tm_ba4f54/debugtraceblockbynumber-way-too-slow-4bg2</link>
      <guid>https://www.xdc.dev/tm_ba4f54/debugtraceblockbynumber-way-too-slow-4bg2</guid>
      <description>&lt;p&gt;hey, running xdc (full syncmode, gcmode archive, not mining) on multiple nodes. We're experiencing weird issue with &lt;code&gt;debug_traceBlockByNumber&lt;/code&gt; calls.&lt;/p&gt;

&lt;p&gt;on 24core AMD (AMD EPYC 7413 24-Core Processor) it takes almost 40secs to get the response, on 12core (Intel(R) Xeon(R) E-2386G CPU @ 3.50GHz) the same query takes 15secs. All the same version, data and configuration, we're using nvme disks.&lt;/p&gt;

&lt;p&gt;query:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;{
    "jsonrpc":"2.0",
        "method":"debug_traceBlockByNumber",
        "params":["0x41A0126", {"tracer": "callTracer", "timeout":"60s"}],
        "id":1
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;24 cores:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;     time_namelookup:  0.000013s
        time_connect:  0.000064s
     time_appconnect:  0.000000s
    time_pretransfer:  0.000084s
       time_redirect:  0.000000s
  time_starttransfer:  33.867162s
                     ----------
          time_total:  33.867536s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;12cores:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;     time_namelookup:  0.000038s
        time_connect:  0.000198s
     time_appconnect:  0.000000s
    time_pretransfer:  0.000260s
       time_redirect:  0.000000s
  time_starttransfer:  15.226504s
                     ----------
          time_total:  15.226841s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;we have issue even with these 15secs, is that a common response time?&lt;/p&gt;

&lt;p&gt;Any idea about possible tuning? Saw that cache is disabled, no LRU cache, no new tracers as in geth&lt;/p&gt;

&lt;p&gt;thanks&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
