servediff 0.1.0__tar.gz

servediff-0.1.0/CHANGELOG.md

@@ -0,0 +1,15 @@
+# Changelog
+
+## 0.1.0 — 2026-10-29
+
+First version.
+
+- `servediff show <log>`: effective configuration facts from a vLLM or SGLang startup log,
+  each with the line it came from.
+- `servediff diff <a.log> <b.log>`: version, arguments, attention / MoE backend, CUDA graph
+  mode and captures, model runner, UVA fallback, startup outcome and root-cause error.
+  Warns when one side failed to start. Errors after the server is ready are hidden unless
+  `--all`.
+- `servediff env [--python PATH]`: snapshot package versions, GPU and engine env vars of a
+  server environment, with secret-looking values redacted. `servediff diff` on two
+  snapshots lists inference-relevant changes first.

servediff-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,22 @@
+# Contributing
+
+The most useful contribution is a **log line servediff missed**.
+
+1. Run `servediff show your-server.log` and find the setting that is `<absent>` but is
+   printed in the log.
+2. Open an issue with the engine version and the exact log line(s). Remove paths,
+   hostnames and anything private first.
+3. For a pull request: add the lines as a fixture under `tests/fixtures/` (say where they
+   came from in `tests/fixtures/README.md`), add a test, then the rule in
+   `src/servediff/cli.py`.
+
+```bash
+pip install -e ".[dev]"
+pytest -q
+```
+
+Rules for new facts:
+
+- A fact comes from a line the server printed. No defaults, no guessing.
+- If the same setting is printed in several formats across versions, one rule should
+  cover them, with a fixture for each format.

servediff-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

servediff-0.1.0/MANIFEST.in

@@ -0,0 +1,3 @@
+include CHANGELOG.md CONTRIBUTING.md README.zh-CN.md
+recursive-include tests/fixtures *.log *.md
+recursive-include examples *.log

servediff-0.1.0/PKG-INFO

@@ -0,0 +1,168 @@
+Metadata-Version: 2.4
+Name: servediff
+Version: 0.1.0
+Summary: Diff what your vLLM / SGLang server actually ran with: auto-selected backends, CUDA graphs, startup failures, dependency versions.
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/apex-mochen/servediff
+Project-URL: Issues, https://github.com/apex-mochen/servediff/issues
+Project-URL: Changelog, https://github.com/apex-mochen/servediff/blob/main/CHANGELOG.md
+Keywords: vllm,sglang,llm-inference,performance-regression,debugging
+Classifier: Programming Language :: Python :: 3
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: Software Development :: Debuggers
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Dynamic: license-file
+
+# servediff
+
+**Same flags, different server.** `servediff` shows what your vLLM or SGLang server
+*actually* ran with — and what changed between two runs.
+
+Benchmark result files only record the client side. After an upgrade, the server can
+silently pick a different MoE or attention backend, change its CUDA graph capture,
+fall back to another code path, or run against different torch / triton / flashinfer
+builds. Today you find that by reading startup logs and bisecting by hand.
+`servediff` does the reading for you.
+
+- **Who it is for:** anyone comparing two vLLM / SGLang runs — after an upgrade, a flag
+  change, or between machines — who needs to know *what differs on the server side*.
+- **What it reads:** the server's startup log, and optionally a snapshot of the
+  server's Python environment. Offline, no GPU, no dependencies.
+- **What it does not do:** it does not say *which* difference caused a performance
+  change. That still needs an A/B run. It tells you what to A/B.
+
+## Try it in one minute (no GPU)
+
+```bash
+git clone https://github.com/apex-mochen/servediff && cd servediff
+pip install .
+servediff diff examples/issue-excerpts/vllm-47047-v0.23-default.log examples/issue-excerpts/vllm-47047-v0.23-marlin.log
+```
+
+```text
+fact                             baseline                                 candidate                                status
+backend.moe                      VLLM_CUTLASS (NvFp4)                     MARLIN (NvFp4)                           changed
+
+1 difference(s); 0 fact(s) identical. Absent means the log did not print it, not that it was off.
+```
+
+That is the difference the reporter of
+[vllm#47047](https://github.com/vllm-project/vllm/issues/47047) found by hand after a
+v0.21 → v0.23 throughput drop. The example files are the log lines posted in that
+issue (see [tests/fixtures/README.md](https://github.com/apex-mochen/servediff/blob/main/tests/fixtures/README.md)).
+
+## Real example: same flags, vLLM 0.28.0 vs 0.30.0
+
+Two startup logs from one RTX 4060 Laptop under WSL2, identical flags
+(Qwen2.5-0.5B-Instruct, fp16, `--max-model-len 2048`, `--gpu-memory-utilization 0.45`):
+
+```bash
+servediff diff vllm-0.28.0.log vllm-0.30.0.log
+```
+
+```text
+warning: baseline server failed to start: RuntimeError: UVA is not available; facts after the failure are absent because startup stopped, not because they were off
+
+fact                             baseline                                 candidate                                status
+backend.attention                <absent>                                 FLASH_ATTN                               only_candidate
+backend.flash_attn_version       <absent>                                 2                                        only_candidate
+backend.sampling_flashinfer      <absent>                                 disabled                                 only_candidate
+cuda_graph.captures              <absent>                                 ["PIECEWISE x51", "FULL x2", "FULL x35"] only_candidate
+cuda_graph.pool_gib              <absent>                                 0.17                                     only_candidate
+engine.version                   0.28.0                                   0.30.0                                   changed
+startup                          failed                                   ready                                    changed
+startup.error                    ["RuntimeError: UVA is not available", " <absent>                                 only_baseline
+uva_buffers                      <absent>                                 fallback: device memory                  only_candidate
+
+9 difference(s); 8 fact(s) identical. Absent means the log did not print it, not that it was off.
+```
+
+0.28.0 does not start on WSL2 with default settings; 0.30.0 does, because it falls
+back to device memory when pinned memory is unavailable. Upstream fixed this in
+[vllm#56908](https://github.com/vllm-project/vllm/pull/56908), first released in
+v0.30.0. Forcing the V1 model runner on 0.28.0 (`VLLM_USE_V2_MODEL_RUNNER=0`) makes it
+start, and the remaining server-side differences are:
+
+```text
+fact                             baseline                                 candidate                                status
+cuda_graph.captures              ["mixed prefill-decode, PIECEWISE x51",  ["PIECEWISE x51", "FULL x2", "FULL x35"] changed
+cuda_graph.pool_gib              0.36                                     0.17                                     changed
+engine.version                   0.28.0                                   0.30.0                                   changed
+model_runner                     <absent>                                 V2                                       only_candidate
+uva_buffers                      <absent>                                 fallback: device memory                  only_candidate
+
+5 difference(s); 11 fact(s) identical. Absent means the log did not print it, not that it was off.
+```
+
+## Dependency versions: `servediff env`
+
+Logs do not print torch / triton / flashinfer versions, and upgrades of those change
+server behaviour too. Snapshot each server environment with its own interpreter —
+nothing needs to be installed into it:
+
+```bash
+servediff env --python /path/to/old-venv/bin/python -o old.json
+servediff env --python /path/to/new-venv/bin/python -o new.json
+servediff diff old.json new.json
+```
+
+Excerpt from the same two environments (20 inference-relevant rows; 74 other packages
+hidden unless you pass `--all`):
+
+```text
+pkg.flashinfer-python            0.6.16.post3                             0.6.18.post1                             changed
+pkg.nvidia-cuda-nvcc             13.3.73                                  13.0.88                                  changed
+pkg.nvidia-cutlass-dsl           4.6.2                                    4.7.1                                    changed
+pkg.torch                        2.13.0                                   2.13.0+cu130                             changed
+pkg.transformers                 5.16.1                                   5.17.0                                   changed
+pkg.vllm                         0.28.0                                   0.30.0                                   changed
+```
+
+Note the older vLLM environment carries *newer* CUDA toolkit wheels (13.3 vs 13.0).
+Whether that matters for performance is not known — that is what an A/B run is for.
+Versions are read from package metadata, so the same torch build can show as `2.13.0`
+in one environment and `2.13.0+cu130` in another.
+
+The snapshot records Python, GPU name and driver (via `nvidia-smi`), all installed
+package versions, and env vars starting with `VLLM_`, `SGLANG_`, `SGL_`, `CUDA_`,
+`NCCL_`, `TORCH_`, `PYTORCH_`, `FLASHINFER_`, `TRITON_`. Values of variables whose name
+contains `TOKEN`, `KEY`, `SECRET`, `PASSWORD`, `CREDENTIAL` or `AUTH` are replaced with
+`<redacted>`. Snapshots and logs contain local paths: review them before sharing.
+
+## What it extracts
+
+| Fact | vLLM | SGLang |
+|---|---|---|
+| version | banner / engine init | — (not printed) |
+| arguments | `non-default args` | `server_args` (all args) |
+| attention backend | `Using X attention backend` | `attention_backend` arg |
+| MoE backend | three log formats seen in 0.23–0.30 | `moe_runner_backend` arg |
+| CUDA graph | eager mode, `cudagraph_mode`, capture sets, pool size | prefill CUDA graph disabled |
+| model runner, UVA fallback | `Using V2 Model Runner`, pinned-memory fallback | — |
+| startup outcome | ready / failed + root-cause error | ready |
+
+Every fact keeps the log line it came from (`servediff show <log>` or `--json`).
+A fact the log did not print is `<absent>`: servediff never fills in defaults.
+Options shared by both engines (dtype, context length, memory fraction, prefix cache,
+CUDA graph, TP size) are mapped to common names, so a vLLM log and an SGLang log can be
+compared, though the result is noisier than a same-engine diff.
+
+Exit codes: `0` no differences, `1` differences, `2` nothing recognised.
+
+## Limits
+
+- Tested on: log excerpts posted in vllm#47047 (v0.23) and vllm#53472 (v0.23, v0.26);
+  full startup logs of vLLM 0.28.0 and 0.30.0 and one SGLang log, all single-GPU with a
+  dense model. TP > 1, MoE models in full logs, and other versions are not yet verified.
+- Parsing is regex-based on log text, which changes between versions. A missed line
+  shows up as `<absent>`, never as a wrong value — please report it.
+
+## License
+
+Apache-2.0.

servediff-0.1.0/README.md

@@ -0,0 +1,147 @@
+# servediff
+
+**Same flags, different server.** `servediff` shows what your vLLM or SGLang server
+*actually* ran with — and what changed between two runs.
+
+Benchmark result files only record the client side. After an upgrade, the server can
+silently pick a different MoE or attention backend, change its CUDA graph capture,
+fall back to another code path, or run against different torch / triton / flashinfer
+builds. Today you find that by reading startup logs and bisecting by hand.
+`servediff` does the reading for you.
+
+- **Who it is for:** anyone comparing two vLLM / SGLang runs — after an upgrade, a flag
+  change, or between machines — who needs to know *what differs on the server side*.
+- **What it reads:** the server's startup log, and optionally a snapshot of the
+  server's Python environment. Offline, no GPU, no dependencies.
+- **What it does not do:** it does not say *which* difference caused a performance
+  change. That still needs an A/B run. It tells you what to A/B.
+
+## Try it in one minute (no GPU)
+
+```bash
+git clone https://github.com/apex-mochen/servediff && cd servediff
+pip install .
+servediff diff examples/issue-excerpts/vllm-47047-v0.23-default.log examples/issue-excerpts/vllm-47047-v0.23-marlin.log
+```
+
+```text
+fact                             baseline                                 candidate                                status
+backend.moe                      VLLM_CUTLASS (NvFp4)                     MARLIN (NvFp4)                           changed
+
+1 difference(s); 0 fact(s) identical. Absent means the log did not print it, not that it was off.
+```
+
+That is the difference the reporter of
+[vllm#47047](https://github.com/vllm-project/vllm/issues/47047) found by hand after a
+v0.21 → v0.23 throughput drop. The example files are the log lines posted in that
+issue (see [tests/fixtures/README.md](https://github.com/apex-mochen/servediff/blob/main/tests/fixtures/README.md)).
+
+## Real example: same flags, vLLM 0.28.0 vs 0.30.0
+
+Two startup logs from one RTX 4060 Laptop under WSL2, identical flags
+(Qwen2.5-0.5B-Instruct, fp16, `--max-model-len 2048`, `--gpu-memory-utilization 0.45`):
+
+```bash
+servediff diff vllm-0.28.0.log vllm-0.30.0.log
+```
+
+```text
+warning: baseline server failed to start: RuntimeError: UVA is not available; facts after the failure are absent because startup stopped, not because they were off
+
+fact                             baseline                                 candidate                                status
+backend.attention                <absent>                                 FLASH_ATTN                               only_candidate
+backend.flash_attn_version       <absent>                                 2                                        only_candidate
+backend.sampling_flashinfer      <absent>                                 disabled                                 only_candidate
+cuda_graph.captures              <absent>                                 ["PIECEWISE x51", "FULL x2", "FULL x35"] only_candidate
+cuda_graph.pool_gib              <absent>                                 0.17                                     only_candidate
+engine.version                   0.28.0                                   0.30.0                                   changed
+startup                          failed                                   ready                                    changed
+startup.error                    ["RuntimeError: UVA is not available", " <absent>                                 only_baseline
+uva_buffers                      <absent>                                 fallback: device memory                  only_candidate
+
+9 difference(s); 8 fact(s) identical. Absent means the log did not print it, not that it was off.
+```
+
+0.28.0 does not start on WSL2 with default settings; 0.30.0 does, because it falls
+back to device memory when pinned memory is unavailable. Upstream fixed this in
+[vllm#56908](https://github.com/vllm-project/vllm/pull/56908), first released in
+v0.30.0. Forcing the V1 model runner on 0.28.0 (`VLLM_USE_V2_MODEL_RUNNER=0`) makes it
+start, and the remaining server-side differences are:
+
+```text
+fact                             baseline                                 candidate                                status
+cuda_graph.captures              ["mixed prefill-decode, PIECEWISE x51",  ["PIECEWISE x51", "FULL x2", "FULL x35"] changed
+cuda_graph.pool_gib              0.36                                     0.17                                     changed
+engine.version                   0.28.0                                   0.30.0                                   changed
+model_runner                     <absent>                                 V2                                       only_candidate
+uva_buffers                      <absent>                                 fallback: device memory                  only_candidate
+
+5 difference(s); 11 fact(s) identical. Absent means the log did not print it, not that it was off.
+```
+
+## Dependency versions: `servediff env`
+
+Logs do not print torch / triton / flashinfer versions, and upgrades of those change
+server behaviour too. Snapshot each server environment with its own interpreter —
+nothing needs to be installed into it:
+
+```bash
+servediff env --python /path/to/old-venv/bin/python -o old.json
+servediff env --python /path/to/new-venv/bin/python -o new.json
+servediff diff old.json new.json
+```
+
+Excerpt from the same two environments (20 inference-relevant rows; 74 other packages
+hidden unless you pass `--all`):
+
+```text
+pkg.flashinfer-python            0.6.16.post3                             0.6.18.post1                             changed
+pkg.nvidia-cuda-nvcc             13.3.73                                  13.0.88                                  changed
+pkg.nvidia-cutlass-dsl           4.6.2                                    4.7.1                                    changed
+pkg.torch                        2.13.0                                   2.13.0+cu130                             changed
+pkg.transformers                 5.16.1                                   5.17.0                                   changed
+pkg.vllm                         0.28.0                                   0.30.0                                   changed
+```
+
+Note the older vLLM environment carries *newer* CUDA toolkit wheels (13.3 vs 13.0).
+Whether that matters for performance is not known — that is what an A/B run is for.
+Versions are read from package metadata, so the same torch build can show as `2.13.0`
+in one environment and `2.13.0+cu130` in another.
+
+The snapshot records Python, GPU name and driver (via `nvidia-smi`), all installed
+package versions, and env vars starting with `VLLM_`, `SGLANG_`, `SGL_`, `CUDA_`,
+`NCCL_`, `TORCH_`, `PYTORCH_`, `FLASHINFER_`, `TRITON_`. Values of variables whose name
+contains `TOKEN`, `KEY`, `SECRET`, `PASSWORD`, `CREDENTIAL` or `AUTH` are replaced with
+`<redacted>`. Snapshots and logs contain local paths: review them before sharing.
+
+## What it extracts
+
+| Fact | vLLM | SGLang |
+|---|---|---|
+| version | banner / engine init | — (not printed) |
+| arguments | `non-default args` | `server_args` (all args) |
+| attention backend | `Using X attention backend` | `attention_backend` arg |
+| MoE backend | three log formats seen in 0.23–0.30 | `moe_runner_backend` arg |
+| CUDA graph | eager mode, `cudagraph_mode`, capture sets, pool size | prefill CUDA graph disabled |
+| model runner, UVA fallback | `Using V2 Model Runner`, pinned-memory fallback | — |
+| startup outcome | ready / failed + root-cause error | ready |
+
+Every fact keeps the log line it came from (`servediff show <log>` or `--json`).
+A fact the log did not print is `<absent>`: servediff never fills in defaults.
+Options shared by both engines (dtype, context length, memory fraction, prefix cache,
+CUDA graph, TP size) are mapped to common names, so a vLLM log and an SGLang log can be
+compared, though the result is noisier than a same-engine diff.
+
+Exit codes: `0` no differences, `1` differences, `2` nothing recognised.
+
+## Limits
+
+- Tested on: log excerpts posted in vllm#47047 (v0.23) and vllm#53472 (v0.23, v0.26);
+  full startup logs of vLLM 0.28.0 and 0.30.0 and one SGLang log, all single-GPU with a
+  dense model. TP > 1, MoE models in full logs, and other versions are not yet verified.
+- Parsing is regex-based on log text, which changes between versions. A missed line
+  shows up as `<absent>`, never as a wrong value — please report it.
+
+## License
+
+Apache-2.0.

servediff-0.1.0/README.zh-CN.md

@@ -0,0 +1,46 @@
+# servediff（中文说明）
+
+**参数一样，server 却不一样。** `servediff` 告诉你 vLLM / SGLang server **实际**用了什么配置，以及两次运行之间哪里变了。
+
+benchmark 结果文件只记录客户端。升级之后，server 可能会悄悄换掉 MoE 或 attention backend、改变 CUDA graph 的捕获方式、走另一条回退路径，或者底下的 torch / triton / flashinfer 版本已经不同。现在要发现这些，只能人工读启动日志、逐个 bisect。servediff 替你把日志读一遍。
+
+- **适合谁**：比较两次 vLLM / SGLang 运行的人，比如升级前后、改了某个参数、换了机器。
+- **读什么**：server 的启动日志；也可以读一份 server Python 环境的快照。离线运行，不需要 GPU，没有任何依赖。
+- **不做什么**：不判断性能变化是哪一项造成的，那仍然需要 A/B 实验。它告诉你该 A/B 哪几项。
+
+## 一分钟试用（不需要 GPU）
+
+```bash
+git clone https://github.com/apex-mochen/servediff && cd servediff
+pip install .
+servediff diff examples/issue-excerpts/vllm-47047-v0.23-default.log examples/issue-excerpts/vllm-47047-v0.23-marlin.log
+```
+
+输出只有一行差异：MoE backend 从 `VLLM_CUTLASS (NvFp4)` 变为 `MARLIN (NvFp4)`。这正是 [vllm#47047](https://github.com/vllm-project/vllm/issues/47047) 的报告者在 v0.21 → v0.23 吞吐下降后，靠人工找出来的差异。
+
+## 真实案例：参数相同，vLLM 0.28.0 对 0.30.0
+
+在一台 RTX 4060 Laptop（WSL2）上，两个版本用完全相同的参数启动：
+
+- 0.28.0 默认配置**起不来**，报 `RuntimeError: UVA is not available`。
+- 0.30.0 能起来，因为 pinned memory 不可用时会回退到 device memory。上游修复是 [vllm#56908](https://github.com/vllm-project/vllm/pull/56908)，v0.30.0 是第一个包含它的正式版。
+
+servediff 会先给出"baseline 启动失败"的 warning 和根因，再列出两边的配置差异。完整输出见英文 README。
+
+## 依赖版本：`servediff env`
+
+```bash
+servediff env --python /旧环境/bin/python -o old.json
+servediff env --python /新环境/bin/python -o new.json
+servediff diff old.json new.json
+```
+
+默认只显示和推理相关的包、GPU、引擎环境变量；其他包要加 `--all` 才列出。名字里含 `TOKEN`、`KEY`、`SECRET`、`PASSWORD` 等的环境变量，值一律替换成 `<redacted>`。快照和日志里有本机路径，分享之前请先检查。
+
+## 边界
+
+- 已测试：vllm#47047、#53472 里贴出的日志片段（v0.23、v0.26），vLLM 0.28.0 / 0.30.0 的完整启动日志，以及一份 SGLang 日志。都是单卡、dense 模型。
+- TP>1、完整日志里的 MoE 模型、其他版本，都还没有验证。
+- 识别不到的行会显示为 `<absent>`，不会显示成错误的值。
+
+许可证：Apache-2.0。

servediff-0.1.0/examples/issue-excerpts/vllm-47047-v0.23-default.log

@@ -0,0 +1 @@
+Using 'VLLM_CUTLASS' NvFp4 MoE backend

servediff-0.1.0/examples/issue-excerpts/vllm-47047-v0.23-marlin.log

@@ -0,0 +1,2 @@
+Using 'MARLIN' NvFp4 MoE backend
+Maximum concurrency for 81,920 tokens per request: 54.14x

servediff-0.1.0/examples/issue-excerpts/vllm-53472-v0.23.log

@@ -0,0 +1,2 @@
+INFO [unquantized.py:291] Using FlashInfer CUTLASS Unquantized MoE backend out of potential
+backends: ['FlashInfer TRTLLM', 'FlashInfer CUTLASS', 'TRITON', 'BATCHED_TRITON'].

servediff-0.1.0/examples/issue-excerpts/vllm-53472-v0.26-flag.log

@@ -0,0 +1,2 @@
+Using MoEPrepareAndFinalizeNoDPEPModular
+Using FlashInferExperts MoE backend

servediff-0.1.0/examples/issue-excerpts/vllm-53472-v0.26.log

@@ -0,0 +1,2 @@
+INFO [unquantized.py:374] Using MoEPrepareAndFinalizeNoDPEPMonolithic
+INFO [unquantized.py:375] Using TrtLlmBf16ExpertsMonolithic MoE backend