RRepoGEO

REPOGEO REPORT · LITE

microsoft/sarathi-serve

Default branch main · commit 96f99117 · scanned 6/4/2026, 11:36:34 PM

GitHub: 505 stars · 63 forks

AI VISIBILITY SCORE
28 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
2 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface microsoft/sarathi-serve, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition the README's opening statement to highlight core differentiator

    Why:

    CURRENT
    Sarathi-Serve is a high througput and low-latency LLM serving framework. Please refer to our OSDI'24 paper for more details.
    COPY-PASTE FIX
    Sarathi-Serve is an advanced LLM serving framework that optimizes GPU utilization for high throughput and low latency through fine-grained scheduling and memory management. It extends existing solutions like vLLM to tackle the throughput-latency tradeoff in LLM inference, as detailed in our OSDI'24 paper.
  • mediumtopics#2
    Expand repository topics with more specific keywords

    Why:

    CURRENT
    llama, llm-inference, pytorch, transformer
    COPY-PASTE FIX
    llama, llm-inference, pytorch, transformer, llm-serving, gpu-optimization, high-throughput, low-latency, inference-engine
  • mediumhomepage#3
    Add a homepage URL to the repository's About section

    Why:

    COPY-PASTE FIX
    https://www.usenix.org/conference/osdi24/presentation/agrawal

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface microsoft/sarathi-serve
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
NVIDIA TensorRT-LLM
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. NVIDIA TensorRT-LLM · recommended 1×
  2. vLLM · recommended 1×
  3. Hugging Face TGI · recommended 1×
  4. DeepSpeed-MII · recommended 1×
  5. OpenVINO · recommended 1×
  • CATEGORY QUERY
    How to achieve high throughput and low latency for large language model inference?
    you: not recommended
    AI recommended (in order):
    1. NVIDIA TensorRT-LLM
    2. vLLM
    3. Hugging Face TGI
    4. DeepSpeed-MII
    5. OpenVINO
    6. ONNX Runtime
    7. TorchServe

    AI recommended 7 alternatives but never named microsoft/sarathi-serve. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are the best serving frameworks for optimizing LLM inference performance on GPUs?
    you: not recommended
    AI recommended (in order):
    1. vLLM (vllm-project/vllm)
    2. Triton Inference Server (triton-inference-server/server)
    3. FasterTransformer (NVIDIA/FasterTransformer)
    4. DeepSpeed-MII (microsoft/DeepSpeed-MII)
    5. TensorRT-LLM (NVIDIA/TensorRT-LLM)
    6. OpenVINO (openvinotoolkit/openvino)
    7. LightLLM (ModelTC/lightllm)

    AI recommended 7 alternatives but never named microsoft/sarathi-serve. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of microsoft/sarathi-serve?
    pass
    AI named microsoft/sarathi-serve explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts microsoft/sarathi-serve in production, what risks or prerequisites should they evaluate first?
    pass
    AI named microsoft/sarathi-serve explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo microsoft/sarathi-serve solve, and who is the primary audience?
    pass
    AI did not name microsoft/sarathi-serve — likely talking about a different project

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of microsoft/sarathi-serve. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/microsoft/sarathi-serve.svg)](https://repogeo.com/en/r/microsoft/sarathi-serve)
HTML
<a href="https://repogeo.com/en/r/microsoft/sarathi-serve"><img src="https://repogeo.com/badge/microsoft/sarathi-serve.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

microsoft/sarathi-serve — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite