Hugging Face
Models
Datasets
Spaces
Buckets
new
Docs
Enterprise
Pricing
Website
Tasks
HuggingChat
Collections
Languages
Organizations
Community
Blog
Posts
Daily Papers
Hardware
Learn
Discord
Forum
GitHub
Solutions
Team & Enterprise
Hugging Face PRO
Enterprise Support
Inference Providers
Inference Endpoints
Storage Buckets
Log In
Sign Up
Orkut Murat YΔ±lmaz
orkut
6
143
Follow
radmard's profile picture
yunusserhat's profile picture
leylabudak's profile picture
23 followers
Β·
104 following
orkutmuratyilmaz
AI & ML interests
Geo Sciences, Free Software
Recent Activity
reacted
to
OppaAI
's
post
with π§
7 days ago
Benchmark test: Jev vs. Laya-ONNX (multilingual) vs. Harrier OSS 270M embedder π¬ My AI wAIfu (Jetson Orin Nano 8GB) uses Harrier OSS 270M for semantic routing in 2 places. It reads vectors of router prompts (English only) and calculates cosine similarity: - Quaternary routing: greeting, local chat (no websearch), web chat (needs websearch), or agentic chat - Agentic routing: which tools in my AI's capability list to use Benchmarked the 2 most hyped decision models β Jev and Laya (ONNX, multilingual) β against Harrier OSS 270M. Setup: 221 quaternary + 58 capability-trigger examples, leave-one-out eval, argmax, no thresholds. Results: β Harrier-270M (local, cosine): 94.6% / 93.1% accuracy, 17ms P50 β‘ β Jev API (hosted): 82.4% / 94.8% accuracy, ~195ms P50 β Laya-ONNX multilingual (fp16, local): 48.0% / 20.7% accuracy, 25-40ms P50 Conclusion: π« Laya is out of the question. 4 of 7 capability categories at 0.0% accuracy while reporting 80-90% confidence means it needs real training before it's practical. βοΈ Jev is a cloud API, not sure it can be trained further. Accuracy is high but not improvable on my end. Latency is ~10x my local embedder (network latency). Input token cost, though small, is still more than $0. Not fully sure about privacy implications either. β Embedding is only semantic cosine similarity, not real reasoning. But it's already doing double duty for memory extraction and RAG β no extra RAM or token cost. Latency is 17ms, accuracy in the 90s%. Even tried Japanese/Chinese prompts, still got high accuracy with only English exemplars. Bigger advantage: I just add exemplars to boost accuracy. When I add/modify/remove tools β often β no retraining needed, just update exemplars, vectors recompute once. Turns out my self-invented routing method, built ~6 months ago, already solved what these now hyped up models β beating Jev and Laya on latency and convenience, matching/beating on accuracy. π―
reacted
to
OppaAI
's
post
with π₯
7 days ago
Benchmark test: Jev vs. Laya-ONNX (multilingual) vs. Harrier OSS 270M embedder π¬ My AI wAIfu (Jetson Orin Nano 8GB) uses Harrier OSS 270M for semantic routing in 2 places. It reads vectors of router prompts (English only) and calculates cosine similarity: - Quaternary routing: greeting, local chat (no websearch), web chat (needs websearch), or agentic chat - Agentic routing: which tools in my AI's capability list to use Benchmarked the 2 most hyped decision models β Jev and Laya (ONNX, multilingual) β against Harrier OSS 270M. Setup: 221 quaternary + 58 capability-trigger examples, leave-one-out eval, argmax, no thresholds. Results: β Harrier-270M (local, cosine): 94.6% / 93.1% accuracy, 17ms P50 β‘ β Jev API (hosted): 82.4% / 94.8% accuracy, ~195ms P50 β Laya-ONNX multilingual (fp16, local): 48.0% / 20.7% accuracy, 25-40ms P50 Conclusion: π« Laya is out of the question. 4 of 7 capability categories at 0.0% accuracy while reporting 80-90% confidence means it needs real training before it's practical. βοΈ Jev is a cloud API, not sure it can be trained further. Accuracy is high but not improvable on my end. Latency is ~10x my local embedder (network latency). Input token cost, though small, is still more than $0. Not fully sure about privacy implications either. β Embedding is only semantic cosine similarity, not real reasoning. But it's already doing double duty for memory extraction and RAG β no extra RAM or token cost. Latency is 17ms, accuracy in the 90s%. Even tried Japanese/Chinese prompts, still got high accuracy with only English exemplars. Bigger advantage: I just add exemplars to boost accuracy. When I add/modify/remove tools β often β no retraining needed, just update exemplars, vectors recompute once. Turns out my self-invented routing method, built ~6 months ago, already solved what these now hyped up models β beating Jev and Laya on latency and convenience, matching/beating on accuracy. π―
liked
a model
11 days ago
prism-ml/Ternary-Bonsai-2-27B-gguf
View all activity
Organizations
models
0
None public yet
datasets
0
None public yet