Project 26: AI-Powered Diagnostic Agent for Edge Devices #34444
AmanjhaMrMajnu
started this conversation in
Google Summer of Code
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi mentors,
During my exploration of Project 26, I've been pondering on the architectural trade-offs between:
A) A purely LLM-based diagnostic pipeline
B) A hybrid approach that uses a combination of deterministic rule-based log pattern matching, lightweight embedding retrieval (RAG), and LLM for root cause summarization
Considering the edge device limitations (in terms of memory, connectivity, and CPU-only inference), I'm trying to comprehend the trade-offs between:
Is there a preference for a deterministic anomaly detection-focused diagnostic agent that uses the LLM for additional reasoning?
Is there an advantage to utilizing small-sized OpenVINO-optimized language models (e.g., 3B-7B quantized models) over API-based models?
Is there an assumption that this project would interface with existing OpenVINO telemetry/benchmarking tools?
Also, I'd like to understand the evaluation criteria better:
What would mentors consider successful from a measurable standpoint?
Diagnosis accuracy?
Latency?
Resource optimization on constrained devices?
Decreased manual debugging efforts?
It would be great to understand which architectural path would best align with the overall vision for OpenVINO.
Beta Was this translation helpful? Give feedback.
All reactions