<?xml version='1.0' encoding='utf-8'?>
<?xml-stylesheet type="text/xsl" href="/v2/static/oai2.xsl"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-10-07T13:17:24Z</responseDate>
  <request identifier="oai:figshare.com:article/33877588" metadataPrefix="oai_dc" verb="GetRecord">https://api.figshare.com/v2/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:figshare.com:article/33877588</identifier>
        <datestamp>2026-09-17T08:54:14Z</datestamp>
        <setSpec>category_29005</setSpec>
        <setSpec>category_28999</setSpec>
        <setSpec>category_26548</setSpec>
        <setSpec>item_type_3</setSpec>
        <setSpec>month_year_09_2026</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Raw benchmark artifacts for "Predictable Trading Infrastructure on Many-Core CPUs" (AMD EPYC 9575F)</dc:title>
          <dc:creator>Chaitanya Palghadmal (25007113)</dc:creator>
          <dc:subject>Distributed computing and systems software not elsewhere classified</dc:subject>
          <dc:subject>Performance evaluation</dc:subject>
          <dc:subject>Systems engineering</dc:subject>
          <dc:subject>trading infrastructure</dc:subject>
          <dc:subject>low-latency systems</dc:subject>
          <dc:subject>many-core CPU</dc:subject>
          <dc:subject>AMD EPYC 9575F</dc:subject>
          <dc:subject>operating envelope</dc:subject>
          <dc:subject>latency tail</dc:subject>
          <dc:subject>concurrency scaling</dc:subject>
          <dc:subject>determinism</dc:subject>
          <dc:subject>reproducability</dc:subject>
          <dc:subject>CPU affinity</dc:subject>
          <dc:subject>cache-aware buffer sizing</dc:subject>
          <dc:subject>benchmark</dc:subject>
          <dc:description>&lt;p dir="ltr"&gt;Unedited console and CSV outputs from the benchmark runs behind the preprint "Predictable Trading Infrastructure on Many-Core CPUs: Latency, concurrency, determinism, and repeatability on a single-socket AMD EPYC 9575F" (Chaitanya Palghadmal, Reamer Labs).&lt;/p&gt;&lt;p dir="ltr"&gt;Every figure in the paper traces to one of the files in this archive. The data characterizes a measurable operating envelope for a composable research-and-execution trading stack: the cost of the integration boundary, end-to-end order latency through the execution core, the 1-to-512 concurrent-strategy curve, research-engine determinism and per-call latency variance across 2,000 runs, execution-core run-to-run variance and how CPU affinity controls it, and the interaction between event-buffer size and CPU-cache behavior.&lt;/p&gt;&lt;p dir="ltr"&gt;All runs come from one machine on one date (2026-09-13). Environment: AMD EPYC 9575F, 1 socket, 64 cores / 128 threads, single NUMA node, Ubuntu 24.04 LTS 64-bit, performance CPU governor, GCC 13 and Go 1.26.4, execution-core build -O2 Release and research build -O3 -funroll-loops -march=native (AVX-512, znver5). Full provenance is in provenance.txt.&lt;/p&gt;&lt;p dir="ltr"&gt;Latency figures are core-only: no venue, no network path, and no Go/Python/FIX binding sit in the latency-critical measurements, so the numbers reflect the execution core rather than the harness around it. The data establishes an operating envelope, not a guaranteed service level. Reproduce on your own target hardware before relying on any specific number. A README in the archive maps each file to the paper section it supports; where the paper and a raw file appear to differ, the raw file is authoritative.&lt;br&gt;&lt;br&gt;Reamer Labs: Quantitative Trading Solutions for mid-frequency quants: a research engine and an execution server, built to institutional standards, each a stable C ABI you link into your own stack. https://reamerlabs.com&lt;/p&gt;</dc:description>
          <dc:date>2026-09-17T08:54:14Z</dc:date>
          <dc:type>Dataset</dc:type>
          <dc:type>Dataset</dc:type>
          <dc:identifier>10.6084/m9.figshare.33877588.v2</dc:identifier>
          <dc:relation>https://figshare.com/articles/dataset/Raw_benchmark_artifacts_for_Predictable_Trading_Infrastructure_on_Many-Core_CPUs_AMD_EPYC_9575F_/33877588</dc:relation>
          <dc:rights>CC BY 4.0</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
