@abu_salem.09: #العودة_للمدارس #حارة_الغاوين #ابوسالم

abu_salem.09
abu_salem.09
Open In TikTok:
Region: NL
Sunday 30 August 2026 09:48:41 GMT
27138
914
59
587

Music

Download

Comments

00.__22
🇸🇦𓃴𓍼ོ🦌🇸🇦 :
عوشه بنت مبارك ساطيه وشخصيتها قويه 😂😂😂😂😂😂
2026-08-30 10:55:02
8
aishaalamrii
عايشه :
الولد فاهم اكثر من امه😂
2026-08-30 10:59:06
2
sooa483
صدقه للمرحوم ادم الشامسي :
عاشت عوشوه بنت مبارك عرفتله راعي الباص 😂😂😂
2026-08-30 09:57:02
8
o.23__
٢3 ☘︎︎ :
عزرايين يعزرش 🤣🤣🤣.
2026-08-30 10:10:29
4
casper.337
3𝔅..~ :
😂 صدقها ! طاير من اول يوم و يسير يعقهم من غبشه
2026-08-30 10:45:37
2
gbk3142
GBK :
مبدع بو سالم
2026-08-30 09:57:58
3
dyqtb32lm1sz
dyqtb32lm1sz :
العمل كامل موجود ع يوتوب حارة الغاوين
2026-08-30 10:31:46
2
user35373415770937
كل نفس بما كسبت رهينة :
عسل والله
2026-08-30 09:54:43
2
7anan_95
🇲🇦lحنونه 🇴🇲 :
😂
2026-08-30 11:09:11
0
moosa97777777777777779
Nasser :
مبدعين كثروا من هلمقاطع 😂😂
2026-08-30 11:07:03
0
user2852116988585
بحرينية :
😂😂😂 بالضبط
2026-08-30 11:17:21
0
anfaas1a4
🤍 :
عزرايين اعزرش🤣
2026-08-30 11:27:11
0
user6116134263148
أبناء السلاطيين :
راعي الباص يتحمل مسوليه اطفال وصيانه وتسجيل وتامين والطريق وكل هذا راتبه٤٠٠ ريال ىاص ومحروقات وصيانه وسائق و٤٠٠ وين بتحصل😂😂😂 والحمدلله
2026-08-30 10:55:18
0
user1299145786358
user1299145786358 :
صحيح بيروح يسوق الباص الثاني 😂😂
2026-08-30 11:08:31
0
abdullah_almeqbale0
عبدالله المقبالي :
مبدع يابوسالم
2026-08-30 11:33:58
0
nov11.a
November :
😂 واقع للأسف
2026-08-30 11:13:31
0
ummkulthum63
ummkulthum :
😂😂😂😂😂😂😂ياربي
2026-08-30 10:58:32
0
wss21755
R.M.C_217 :
واقع🤣🤣🤣🤣🤣
2026-08-30 10:00:46
0
oooooo1993
11:59 :
😂😂😂 ادب
2026-08-30 11:34:44
1
haleemaalkaabi
Haleema Alkaabi :
😂
2026-08-30 10:54:13
0
s88ddso
Maestro :
والله أغلبهم كذا يسوو بس الحل بسيط روح اشتكي عليهم ف المديريه وبيجو ع التوقيت اللي حاطته المدرسه
2026-08-30 10:52:04
0
zeyad5833
Ze Yad :
😅😅😅الحين ماحد ياكل شىء
2026-08-30 10:48:02
0
s.a500m
S.A500 :
2026-08-30 10:11:58
0
To see more videos from user @abu_salem.09, please go to the Tikwm homepage.

Other Videos

When an interviewer says “we have millions of customer support tickets…” they’re not testing AI. they’re testing systems thinking. Here’s what that actually looks like 👇 I’d break it into 5 parts: ingestion, embeddings, retrieval, generation, monitoring 1️⃣ Ingestion is offline, not request-time At this scale, everything is async • Stream tickets from DB / event logs • Normalize messy text (typos, threads, duplicates) • Thread conversations properly (not just single messages) • Chunk by conversation flow, not fixed tokens • Attach metadata (user, product, issue type, timestamp) This NEVER touches your request path 2️⃣ Embeddings + indexing built for scale You don’t embed on demand • Batch jobs for new tickets (queue-based) • Distributed vector DB (Qdrant, Milvus, etc.) • Hybrid search (BM25 + dense vectors) • Sharding by product / issue type • Store metadata alongside vectors Key insight: metadata filtering > vector search 3️⃣ Retrieval + generation (tight path) Keep this path fast and lean: query → metadata filter → cache → hybrid search → rerank → LLM • Most queries hit cache • Many never reach vector search • Rerank small candidate sets only • Send 5–10 HIGH quality chunks More data ≠ better answers Relevance wins every time 4️⃣ Caching is everything This is where scale actually happens • FAQ cache (repeat questions) • Retrieval cache (top ticket clusters) • Embedding cache (hot queries) Real flow: query → cache → (miss) retrieve + LLM → store result This is how you cut cost AND latency 5️⃣ Monitoring closes the loop Without this, your system slowly dies • Are we retrieving the right tickets? (recall@k) • Are answers actually helpful? (feedback) • Latency + cache hit rate • Auto re-embed as new tickets come in BOTTOM LINE: RAG at this scale is NOT an AI problem it’s a search + data + caching problem Most engineers build chatbots Real AI engineers build infrastructure #aiengineer #ai #embedding #rag #softwareengineer
When an interviewer says “we have millions of customer support tickets…” they’re not testing AI. they’re testing systems thinking. Here’s what that actually looks like 👇 I’d break it into 5 parts: ingestion, embeddings, retrieval, generation, monitoring 1️⃣ Ingestion is offline, not request-time At this scale, everything is async • Stream tickets from DB / event logs • Normalize messy text (typos, threads, duplicates) • Thread conversations properly (not just single messages) • Chunk by conversation flow, not fixed tokens • Attach metadata (user, product, issue type, timestamp) This NEVER touches your request path 2️⃣ Embeddings + indexing built for scale You don’t embed on demand • Batch jobs for new tickets (queue-based) • Distributed vector DB (Qdrant, Milvus, etc.) • Hybrid search (BM25 + dense vectors) • Sharding by product / issue type • Store metadata alongside vectors Key insight: metadata filtering > vector search 3️⃣ Retrieval + generation (tight path) Keep this path fast and lean: query → metadata filter → cache → hybrid search → rerank → LLM • Most queries hit cache • Many never reach vector search • Rerank small candidate sets only • Send 5–10 HIGH quality chunks More data ≠ better answers Relevance wins every time 4️⃣ Caching is everything This is where scale actually happens • FAQ cache (repeat questions) • Retrieval cache (top ticket clusters) • Embedding cache (hot queries) Real flow: query → cache → (miss) retrieve + LLM → store result This is how you cut cost AND latency 5️⃣ Monitoring closes the loop Without this, your system slowly dies • Are we retrieving the right tickets? (recall@k) • Are answers actually helpful? (feedback) • Latency + cache hit rate • Auto re-embed as new tickets come in BOTTOM LINE: RAG at this scale is NOT an AI problem it’s a search + data + caching problem Most engineers build chatbots Real AI engineers build infrastructure #aiengineer #ai #embedding #rag #softwareengineer

About