Skip to content
プロジェクト

wangxb96/Awesome-EdgeAI has 120 GitHub stars and 22 forks. Star changes are not measured yet. Last checked 2026-11-14 13:50 UTC. Last push 2026-11-13.

この数値の測り方

計測したスター増加

24時間
履歴を収集中
7日間
履歴を収集中
15日間
履歴を収集中
1か月
履歴を収集中

期間ごとの純増数です。期間は重複しており、日別の値ではありません。未計測の値は空欄です。スター数は注目度の指標であり、品質の保証ではありません。

概要

Resources of our survey paper "Optimizing Edge AI: A Comprehensive Survey on Data, Model, and System Strategies" and "Cognitive Edge Computing: A Comprehensive Survey on Optimizing Large Models and AI Agents for Pervasive Deployment"

機械学習

Awesome Edge AI

Awesome Stars License

From data–model–system optimization to cognitive edge computing. A curated guide to compact language and multimodal models, tool-using agents, and the model–runtime–network choices that make them useful on client devices and nearby servers.

A deployment must preserve a declared task outcome while fitting memory, latency, energy, connectivity and trust constraints. This single-page guide follows that decision: what the task requires, which bottleneck a technique changes, where it executes, and what its evidence measures.

Cognitive edge resource map

Contents

Survey versions and repositories

The current public preprint is Cognitive Edge Computing: A Comprehensive Survey on Optimizing Large Models and AI Agents for Pervasive Deployment. The two versions share arXiv identifier 2501.03265 and document the manuscript's progression from the optimization triad to cognitive workloads and agents.

Version Bibliographic record Repository and scope
v1 · 4 January 2025 Xubin Wang and Weijia Jia. Optimizing Edge AI: A Comprehensive Survey on Data, Model, and System Strategies. arXiv:2501.03265v1. Awesome-EdgeAI: the data–model–system resource collection, now maintained here together with the cognitive-edge material.
v2 · 7 November 2025 Xubin Wang, Qing Li and Weijia Jia. Cognitive Edge Computing: A Comprehensive Survey on Optimizing Large Models and AI Agents for Pervasive Deployment. arXiv:2501.03265v2. cognitive-edge-llm-agent-survey: focused LLM/agent literature map; Awesome-EdgeAI: this consolidated guide and the current protocol, census and editable figures.

The associated journal manuscript is titled Cognitive Edge Computing: A Survey on Optimizing Large Language Models and Autonomous Agents for the Edge. Its current reproducibility artifacts are maintained in this repository. Version-specific BibTeX records are provided under Citation.

Deployment framework

  1. Define acceptance. Specify the useful outcome, required evidence, deadline and permitted actions. A valid model response can still be an incomplete user task.
  2. Measure the bottleneck. Separate weights, retained KV, workspace, prefill, decode, tools, communication and sustained thermal behavior.
  3. Choose compatible controls. Context selection, precision, reasoning depth, scheduling and placement change different costs. Verify their interaction on the intended runtime.
  4. Validate the entire episode. Include retries, failed/deferred tasks, tool effects and all declared devices in the accounting. Use task success alongside quality proxies and execution metrics.

For example, a private mobile assistant may retrieve one decisive fact locally, use a compact text model or bounded function caller, validate the proposed tool action, and defer if neither local nor permitted remote execution meets the acceptance conditions. A workstation agent, a phone demonstration and a network simulator support different deployment claims.

Models and runtimes

Choose the model's role before its size. A text model, visual encoder, function caller and orchestration framework provide different components of an application. Released parameter counts are not total resident application memory. Pin the model, tokenizer/template, precision format, runtime and device revision for a run.

Task and resource loops across computing tiers

Role-matched model artifacts

Role Representative artifacts Deployment question
Local text, retrieval and bounded reasoning Qwen3 0.6B/1.7B/4B, Llama 3.2 1B/3B Instruct, SmolLM2 135M/360M/1.7B Does the selected precision and context preserve task correctness within sustained memory/latency limits?
Bounded device actions FunctionGemma 270M, Mobile Actions example Who parses, authorizes, confirms and executes each call? A function caller alone is not an autonomous planner.
Visual and audio assistance Gemma 3n E2B/E4B, FastVLM, MiniCPM-V Include encoder/token cost, conditional loading and modality quality; effective-size labels are not complete RAM estimates.
Low-bit local text BitNet Does the backend execute the intended low-bit kernels, and what quality/traffic trade-off results?
Personal-device agent TinyAgent Are planner, executor, tool state and final task verification all accounted for?

Model reports

Generative inference stacks

Stack Intended execution role Check before comparison
llama.cpp GGUF model execution across supported CPU/GPU and other backends Quantizer revision, actual backend and operator fallback
MLC LLM Compiled deployment to supported mobile, browser and accelerator targets Target build, compilation and model-library compatibility
ExecuTorch PyTorch model export and on-device execution Delegation, supported operators and exported graph
LiteRT / LiteRT-LM On-device ML and generative-model execution Supported model conversion and selected device accelerator
MLX / MLX LM Apple Silicon arrays, language-model generation and adaptation Unified-memory residency and measured device/configuration
ONNX Runtime / GenAI ONNX execution providers and generation loop Execution provider, graph partitions, KV layout and sampling
MNN / ncnn Mobile and embedded inference Model-specific operator and precision support
Transformers.js Browser/JavaScript inference Browser backend, memory limits and model format
TensorRT-LLM Supported NVIDIA accelerator serving Exact GPU/platform support; do not infer phone portability

Use current vendor documentation for Core ML, Qualcomm AI Hub and LiteRT. Version-specific accelerator paths change. Runtime availability does not establish equal capability or performance across targets.

MCU and embedded inference

TensorFlow Lite Micro, CMSIS-NN, TinyEngine and emlearn support constrained inference roles. Their small-network results should not be presented as evidence that a complete LLM agent fits an MCU. See the foundations for the relevant model and training regimes.

Optimization under deployment budgets

Start from a feasible, correct baseline and a measured bottleneck. Weight storage, KV state, visual encoding, decoding, tool calls and wireless transfers compete for different resources. A gain in one phase need not improve complete-task latency or energy.

Shared resource couplings

Context, state and memory

Analytical weight and KV-state memory budget

The analytical memory illustration separates fixed weight storage from context-dependent KV growth. Its CSV is formula-generated, not a device benchmark; workspace and operating-system cost are excluded.

Precision and model structure

Decoding and test-time work

Measure drafting, verification, switching, accepted output and rejected work together. Acceptance rate alone cannot establish speedup, and a reasoning-token cap alone cannot establish preserved task quality.

Runtime, scheduling and hardware mapping

Adaptation and federated learning

Tooling: AWQ, GPTQ, SmoothQuant, OmniQuant, PEFT, bitsandbytes.

Report whether adapters are merged, switched or served concurrently. Base weights, activation memory, communication, update cost and quality drift remain relevant after trainable parameters are reduced.

Agents and applications

An agent combines a model with task state, tools and a stopping policy. The deployment unit is the user goal, including repeated calls and recovery. The same workflow may execute locally, at a gateway or through permitted cloud delegation.

Permissioned assistant workflow

Planning, execution and state

Reasoning budgets and predictive planning

Retrieval-augmented workflows

Context-selection and cached-state mechanisms are in Optimization. Include retrieval index freshness, resident state and evidence recall in the task acceptance check.

Delegation and distributed execution

Three collaboration patterns

Full-request delegation transfers selected evidence; model partitioning transfers intermediate state; a large–small cascade routes between models. Compare like tasks and record payload, state ownership, link conditions, retries and fallback.

LLMs controlling edge networks

Running a model on an edge device and using an LLM to control a network are complementary roles. Assess controller utility, inference overhead, action feasibility and decision deadlines separately.

Application-specific boundaries

A healthcare-oriented model or a smart-home prototype is not, by itself, a validated clinical or production deployment. State the environment, permitted actions, human confirmation and failure handling. The evaluation guide distinguishes these outcomes from token-level quality and runtime speed.

Evaluation and trust

Measure the capability being claimed at the deployment boundary where it matters. Direct task success, language-model quality proxies and execution measurements answer different questions. Publication venue and code availability are separate from whether a result can be reconstructed.

Request and episode accounting

Complete-task outcomes

For A attempted episodes and S successes, report S/A with failed and timed-out attempts included. Mean attempt energy is total attempted-task energy divided by A; amortized energy per success uses the same numerator divided by S and is undefined for S=0. A success-only conditional mean answers a different question. Keep request TTFT and p95 separate from task completion time and deadline satisfaction.

The benchmark protocol specifies future logs, grouping and energy boundaries. The helper summarizes supplied request records and does not reconstruct missing historical traces or infer episode success from call success.

Device and sustained-session studies

Benchmarks: MLPerf Inference, MLPerf Tiny. Record the suite version, task, data split, precision, runtime, memory, thermal state, power scope and independent repetition unit. A global model leaderboard cannot replace a matched deployment study.

Security and privacy

Locality can reduce data transfer but does not establish a complete security guarantee. State the adversary and protected objects, including model weights, retained context, sensor input, tool credentials and action state. Distinguish leakage prevention from permission enforcement and recovery.

Check confidentiality, permission scope, revocation, idempotence, network failure and stale state in the full workflow. Report security overhead on the same workload used for capability and cost measurements. See Foundations and surveys for complementary threat surveys.

Foundations and surveys

These sources provide starting points for mechanisms and neighboring research scopes. Foundational perception, server serving and MCU learning results transfer to cognitive edge workflows only under explicit model, runtime and task conditions.

Edge foundations

Constrained learning foundations

These systems establish important constrained-learning mechanisms; they do not establish full LLM-agent execution on microcontrollers.

Edge language models and collaborative intelligence

Cognitive network control and agentification

The optimization, agent and evaluation guides place primary studies beside the specific mechanism or boundary they address.

Research artifacts and figures

The repository follows the reading guide above. For files, use this directory map; the server archive and synthetic examples have separate entry points.

README.md                 Integrated literature and deployment guide
survey/
  supplement/             Final supplementary PDF and reading guide
  server/                 Recovered requests, provenance and offline reanalysis
  figures/                Editable sources, inputs and publication exports
  examples/               Synthetic request-format examples
  references.bib          Bibliographic source records
  cited_reference_index.json  Exact main/supplement citation inventory
  evidence_ledger.json     Result-specific evidence and artifact boundaries
  *_protocol.md, protocol.md  Scope and measurement contracts

Read the supplementary PDF for source locators, extended deployment checks and the worked assistant contract. The recovered server archive retains the empirical record separately from synthetic helper examples. The repository includes the bibliographic database, figure inputs, protocols and runnable format examples. Editable manuscript sources and author-local build files are not distributed. The current public artifact edition is pinned to tag public-artifacts-2026-11-13-v5.

Artifact Purpose
Supplement PDF Section directory, extended evidence, source locators and deployment contracts
Study evidence ledger Seventeen result-specific publication/artifact snapshots, evaluation paths and transfer limits
Bibliographic database The survey's reference records; broader than the printed reference list
Public-file inventory / closure check All distributed files, supplement dependencies and optional anonymous access checks
Historical server record Recovered requests, task definitions, all-campaign ledger, descriptive reanalysis and measurement-boundary figures
Synthetic request example Runnable CSV and expected JSON for checking the helper's format and denominators; no measured performance
Survey protocol Scope, source verification, E1/E2/E3 publication/artifact qualification and search-record limitations
Reference database Bibliographic records for both survey versions and the current guide
Benchmark protocol Request/episode boundaries, failure accounting and energy attribution
Descriptive analysis helper Summaries of supplied request records; does not infer complete-task success
Literature audit / repository audit Check the linked resources in this README
Editable figure catalogue Sources, vector exports, analytical data and rebuild commands

The manuscript's retained-link census is pinned to commit 82b6110, with 145 arXiv identifiers, 137 title-audited labels and 123 distinct recorded repository URL-root strings (122 after case folding). These are link units, not a study-screening flow; normalization does not resolve redirects or aliases. This living README and its current_* manifests are separate from that frozen snapshot. The protocol explains how to reproduce it.

For this README:

python3 survey/check_docs.py
python3 survey/check_public_artifacts.py
python3 survey/verify_corpus.py --offline
python3 survey/verify_repos.py

The literature command reuses cached primary metadata and reports missing records; the repository command checks live reachability. Version-specific records above were checked against their primary arXiv pages. A successful link check does not establish official ownership, experimental replication or suitability for a particular device.

The supplement is distributed as a rendered PDF; editable manuscript sources and TeX build inputs are not part of this repository. To check the analysis format without collecting measurements:

python3 survey/compute_ci.py \
  --input survey/examples/request_records_synthetic.csv \
  --out request_summary_local.json

The output matches the supplied synthetic summary. The fixture contains invented request statuses and timings only; it cannot validate a model, estimate device performance or restore the historical records. For anonymous access to every distributed file at the pinned edition, run python3 survey/check_public_artifacts.py --online.

Figure sources

Reading purpose Editable source Vector export
Resource map Python PDF, SVG
Cognitive task/resource loops Python PDF, SVG
Analytical weight/KV budget Python, CSV PDF, SVG
Reported quantization / task-score trade-offs Python, source CSV PDF, SVG
Placement, collaboration, shared resources and workflow accounting Python Placement, Collaboration, Couplings, Workflow
Historical server results and interpretation Python, record analysis, CSV Results PDF, boundary-check PDF
Permissioned assistant Python PDF, SVG

The memory illustration is formula-generated under stated assumptions. The quantization panel replots nine published QSpec scores, with no new trials or uncertainty estimates. The two server-record figures use recovered requests and an explicitly conceptual endpoint-power diagram. Remaining figures are conceptual: geometry encodes no measured performance, and pictograms denote roles. The prospective assistant is a synthesis example. Sources share a restrained palette and export editable PDF/SVG plus PNG and 600-dpi TIFF.

Citation

Use the version corresponding to the material being cited.

Initial data–model–system version

@article{wang2025optimizing_v1,
  title={Optimizing Edge AI: A Comprehensive Survey on Data, Model, and System Strategies},
  author={Wang, Xubin and Jia, Weijia},
  journal={arXiv preprint arXiv:2501.03265v1},
  year={2025},
  note={Version 1, January 4, 2025},
  url={https://arxiv.org/abs/2501.03265v1}
}

Cognitive edge computing version

@article{wang2025cognitive_v2,
  title={Cognitive Edge Computing: A Comprehensive Survey on Optimizing Large Models and AI Agents for Pervasive Deployment},
  author={Wang, Xubin and Li, Qing and Jia, Weijia},
  journal={arXiv preprint arXiv:2501.03265v2},
  year={2025},
  note={Version 2, November 7, 2025},
  url={https://arxiv.org/abs/2501.03265v2}
}

Maintained by Xubin Wang, Qing Li and Weijia Jia.

Contribution guide · License

関連プロジェクトを探す