{
  "schema_version": "0.6.0",
  "paper_id": "n-lane-bridge-performance-antipatterns",
  "page_url": "https://naser.github.io/research-publications/papers/n-lane-bridge-performance-antipatterns/",
  "title": "N-Lane Bridge Performance Antipattern Analysis Using System-Level Execution Tracing",
  "title_variants": [],
  "authors": [
    "Riley VanDonge",
    "Naser Ezzati-Jivan"
  ],
  "author_details": [
    {
      "name": "Riley VanDonge",
      "orcid": null,
      "profile_url": "https://dblp.org/pid/333/8400.html"
    },
    {
      "name": "Naser Ezzati-Jivan",
      "orcid": "https://orcid.org/0000-0003-1435-6297",
      "profile_url": "https://naser.github.io/"
    }
  ],
  "publication": {
    "year": 2022,
    "venue": "IEEE Working Conference on Source Code Analysis and Manipulation (SCAM)",
    "type": "conference paper",
    "publication_date": "2022-10",
    "online_date": null,
    "print_date": "2022-10",
    "volume": null,
    "issue": null,
    "pages": "83-93",
    "article_number": null,
    "publisher": "IEEE",
    "issn": [],
    "isbn": [],
    "crossref_type": "proceedings-article"
  },
  "publication_type": "research paper",
  "status": "published_metadata_record",
  "canonical_source_url": "https://doi.org/10.1109/scam55253.2022.00015",
  "source_record_id": "n-lane-bridge-performance-antipattern-analysis-using-system-level-execution-tracing-2e33511755",
  "identifiers": {
    "doi": "10.1109/scam55253.2022.00015"
  },
  "abstract": null,
  "abstract_source": "N-Lane Bridge published-paper PDF reviewed on 2026-08-06; abstract not reproduced because reuse permission for the publisher version was not established.",
  "abstract_available": false,
  "scholar_eligibility": {
    "eligible": false,
    "basis": "not-eligible",
    "note": "The page is a discovery record; it does not claim Google Scholar article-host eligibility."
  },
  "description": "N-Lane Bridge extends One-Lane Bridge analysis to active-resource bottlenecks and uses LTTng system-level traces to distinguish application-caused congestion from external interference.",
  "evidence_level": "metadata-or-abstract-reviewed",
  "evidence": {
    "source_basis": "metadata-only",
    "coverage": "bibliographic metadata",
    "summary_origin": "AI-assisted catalog editorial summary",
    "review_status": "catalog-reviewed; paper-author approval pending",
    "verified_on": "2026-08-09",
    "sources": [
      {
        "note": "Crossref and local DBLP/venue metadata for 10.1109/scam55253.2022.00015"
      },
      {
        "note": "author identity matched to Naser Ezzati-Jivan in the local research catalog"
      },
      {
        "note": "N-Lane Bridge PDF pp. 1-7: OLB/NLB definitions, LTTng 2.12.3, Trace Compass, tracepoints, critical-path and response-time method"
      },
      {
        "note": "N-Lane Bridge PDF pp. 7-9: Firefox 65.0/98.0.2 and InDebitO cases, latency causes, and NLB classification"
      },
      {
        "note": "N-Lane Bridge PDF pp. 9-10: CPU/I/O overhead, trace sizes, offline analysis cost, threats, and future work"
      },
      {
        "note": "local N-Lane Bridge PDF hash verified in pdf-evidence/notes/n-lane-bridge-performance-antipatterns.md and pdf-evidence/extraction-manifest.json"
      }
    ]
  },
  "summary": {
    "core_contribution": "N-Lane Bridge extends One-Lane Bridge analysis to active-resource bottlenecks and uses LTTng system-level traces to distinguish application-caused congestion from external interference.",
    "problem": "Existing One-Lane Bridge methods focus on passive resources and imprecise CPU metrics, so they can miss latency caused by an application's overuse of CPUs, memory, disks, or other active resources.",
    "method": "LTTng 2.12.3 and Trace Compass collect request delimiters, scheduling, wakeup, interrupt, timer, syscall, and call-stack events. Workloads scale users as A+Bx until response time reaches 10 times the baseline; critical paths classify running, preempted, interrupt, timer, network, input, block-device, and unknown-blocked time. A 5% one-tailed unequal-variance t-test detects nonlinear response growth, and average blocking-time increases identify the responsible resource. Active-resource congestion then separates an N-Lane Bridge from an external bottleneck; ELF symbols locate passive-resource code without source instrumentation.",
    "findings": "In Firefox 65.0 PDF.js, average render time rises from 31.6 seconds for one window to 2:16.8 for two and 5:43.0 for three. Poll blocking contributes 54.49% of latency increase, CPU preemption 27.66%, and futex blocking 10.85%; memory paging and CPU occupancy identify active-resource N-Lane Bridges. In the unfamiliar InDebitO Flask application, 36 concurrent login requests produce a 10x latency increase and reveal CPU congestion caused by the application.",
    "limitations": "The method is evaluated on layered systems and its extraction cost grows with threads, traces, and event volume. It is heuristic, can miss antipatterns absent from the recorded workload, may report false negatives when the test system has excess resources, and does not always locate the complete source-level cause.",
    "future_work": "Extend the analysis to Traffic Jam and Ramp antipatterns and investigate software-aging and security-related antipatterns."
  },
  "tags": [
    "kernel-tracing",
    "system-tracing",
    "performance-analysis",
    "anomaly-detection"
  ],
  "keywords": [
    "N-Lane Bridge",
    "One-Lane Bridge",
    "performance antipatterns",
    "system-level execution tracing",
    "LTTng",
    "Trace Compass",
    "sched_switch",
    "sched_wakeup",
    "futex",
    "Firefox PDF.js",
    "InDebitO",
    "SysBench",
    "memory paging",
    "CPU preemption"
  ],
  "versions": [
    {
      "id": "published-version",
      "label": "Published version",
      "relation": "version-of-record",
      "title": "N-Lane Bridge Performance Antipattern Analysis Using System-Level Execution Tracing",
      "url": "https://doi.org/10.1109/scam55253.2022.00015",
      "pdf_url": null,
      "status": "published",
      "canonical_for_citation": true
    }
  ],
  "access": {
    "status": "published_metadata_record",
    "note": "The DOI is the canonical citation target; this catalog does not redistribute the publisher PDF.",
    "license": null
  },
  "resources": {
    "code": null,
    "data": null,
    "slides": null,
    "demo": null
  },
  "citation_guidance": {
    "when_to_cite": "Cite this paper when detecting One-Lane and active-resource N-Lane Bridge performance antipatterns with system-level tracing.",
    "points": [
      "LTTng 2.12.3 and Trace Compass critical-path analysis with scheduling, syscall, interrupt, and call-stack events.",
      "Firefox PDF.js and InDebitO case studies that distinguish memory, CPU, I/O, and futex causes of nonlinear latency.",
      "Measured CPU/I/O tracing overhead and heuristic limitations for layered multi-threaded systems."
    ],
    "canonical_version_id": "published-version"
  },
  "provenance": {
    "metadata_verified_on": "2026-08-09",
    "metadata_source": [
      "Crossref and local DBLP/venue metadata for 10.1109/scam55253.2022.00015",
      "author identity matched to Naser Ezzati-Jivan in the local research catalog",
      "N-Lane Bridge PDF pp. 1-7: OLB/NLB definitions, LTTng 2.12.3, Trace Compass, tracepoints, critical-path and response-time method",
      "N-Lane Bridge PDF pp. 7-9: Firefox 65.0/98.0.2 and InDebitO cases, latency causes, and NLB classification",
      "N-Lane Bridge PDF pp. 9-10: CPU/I/O overhead, trace sizes, offline analysis cost, threats, and future work",
      "local N-Lane Bridge PDF hash verified in pdf-evidence/notes/n-lane-bridge-performance-antipatterns.md and pdf-evidence/extraction-manifest.json"
    ],
    "summary_written_by": "AI-assisted",
    "summary_verified_by": "metadata/abstract-grounded catalog review; full-text review and author approval pending",
    "linked_preprint_record": null,
    "author_order_note": null
  },
  "batch": {
    "phase": 2,
    "batch_label": "expanded forty-paper release",
    "status": "included_in_expanded_catalog",
    "selected_at": "2026-08-09"
  }
}