{ "schema_version": 1, "builder_plan": { "scenario": "Profiling shows attention computation is a bottleneck in your self-hosted service.", "change": "Check the supported GPU, tensor shapes, and precision, then replace only the relevant kernel.", "baseline": "The existing kernel inside the same complete serving pipeline.", "steps": [ "Locate the paper's implementation and check its license, model support, data needs, and hardware requirements. Stop here if you cannot obtain the required artifacts.", "Save a small set of representative product tasks and expected outcomes. Keep evaluation tasks out of any training or tuning, and choose quality and cost limits before running.", "Run the baseline and the proposed change on identical inputs. Keep other settings fixed and repeat paired runs to expose variation.", "Save per-task outputs, failures, timings, and all usage costs. Review regressions before expanding the test." ], "measure": "Numerical differences, end-to-end latency, throughput, and memory at realistic shapes.", "decision": "Keep the change only if it meets your preselected quality and latency limits and improves the metric you care about after setup and operating costs. Otherwise retain the baseline. This is an exploration plan, not a validated recommendation." }, "builder_review": null, "arxiv_id": "2609.29765", "title": "Dense Matrices Are Alike; Sparse Matrices Are Sparse in Their Own Way: A Structure-Adaptive Tile Cholesky Factorization", "summary": "The method replaces the fixed data structure used by conventional sparse direct Cholesky solvers with a per-matrix, per-tile selector that routes computation to dense, semisparse (active-column), or sparse tile representations on one static shared-memory schedule. It costs a one-time symbolic analysis of the factor's sparsity pattern, which only amortizes when the same pattern is factorized repeatedly (it pulls ahead by the third factorization), and the GPU path is limited to the dense regime with the factor resident on the device. It can fail to pay off when sparsity patterns change between factorizations, when matrices are small enough that analysis overhead dominates, or when the workload is inference-centric deep learning rather than SPD systems such as INLA or spatial statistics.", "rationale": "This is a numerical linear algebra solver for repeated sparse SPD factorization, not an ML inference or training optimization, so it is only relevant to the reader if their production workload actually includes such factorizations, for example Bayesian spatial modeling with INLA.", "technique": "Structure-adaptive tile Cholesky factorization", "family": "kernels_e_atencao", "recommendation": "observar", "published": "2026-09-24", "as_of": "2026-10-18", "editorial_status": "indexed", "source_url": "https://arxiv.org/abs/2609.29765", "independent_implementations": 0, "total_implementations": 0, "stars": 0, "citations": 0, "claims": [ { "claim_id": "claim-01", "statement": "The method replaces the fixed data structure used by conventional sparse direct Cholesky solvers with a per-matrix, per-tile selector that routes computation to dense, semisparse (active-column), or sparse tile representations on one static shared-memory schedule. It costs a one-time symbolic analysis of the factor's sparsity pattern, which only amortizes when the same pattern is factorized repeatedly (it pulls ahead by the third factorization), and the GPU path is limited to the dense regime with the factor resident on the device. It can fail to pay off when sparsity patterns change between factorizations, when matrices are small enough that analysis overhead dominates, or when the workload is inference-centric deep learning rather than SPD systems such as INLA or spatial statistics.", "basis": "inferred", "result": "", "baseline": "", "conditions": "", "source_url": "https://arxiv.org/abs/2609.29765", "source_page": null, "source_excerpt": "" }, { "claim_id": "claim-02", "statement": "Summed over 60 SPD matrices, the adaptive selector beats the best fixed single-structure mode by 1.6 to 2.6x and all compared solvers (MUMPS, PaStiX, CHOLMOD, symPACK, PARDISO) by 1.8 to 12.5x on Intel and 2.6 to 10.1x on AMD; a single-A100 dense route is 1.2 to 6.3x faster than the faster CPU node.", "basis": "inferred", "result": "", "baseline": "", "conditions": "", "source_url": "https://arxiv.org/abs/2609.29765", "source_page": null, "source_excerpt": "" } ], "exposure_map": [ { "dimension": "quality", "basis": "not_evaluated", "finding": "", "interpretation": "", "limitation": "", "next_check": "", "source_url": "", "source_page": null, "source_excerpt": "" }, { "dimension": "compute", "basis": "not_evaluated", "finding": "", "interpretation": "", "limitation": "", "next_check": "", "source_url": "", "source_page": null, "source_excerpt": "" }, { "dimension": "latency", "basis": "not_evaluated", "finding": "", "interpretation": "", "limitation": "", "next_check": "", "source_url": "", "source_page": null, "source_excerpt": "" }, { "dimension": "operations", "basis": "not_evaluated", "finding": "", "interpretation": "", "limitation": "", "next_check": "", "source_url": "", "source_page": null, "source_excerpt": "" }, { "dimension": "compatibility", "basis": "not_evaluated", "finding": "", "interpretation": "", "limitation": "", "next_check": "", "source_url": "", "source_page": null, "source_excerpt": "" }, { "dimension": "security", "basis": "not_evaluated", "finding": "", "interpretation": "", "limitation": "", "next_check": "", "source_url": "", "source_page": null, "source_excerpt": "" }, { "dimension": "data_and_training", "basis": "not_evaluated", "finding": "", "interpretation": "", "limitation": "", "next_check": "", "source_url": "", "source_page": null, "source_excerpt": "" }, { "dimension": "reproducibility", "basis": "not_evaluated", "finding": "", "interpretation": "", "limitation": "", "next_check": "", "source_url": "", "source_page": null, "source_excerpt": "" } ], "risks": [], "minimum_test": [], "open_questions": [], "independent_tests": [], "lab_reproductions": [], "report_available": false, "validation_tier": "unknown", "evidence_tier": "unknown", "infrastructure_basis": "unknown", "equations": [], "equations_status": "not_fetched", "core_kind": "", "equations_fetched_at": "", "equations_source_url": "", "equations_source_sha256": "", "exposures_reviewed_at": "", "exposures_source_sha256": "" }