Konspekt · Asoslar
Qog'oz ustida hisob
Muammo
Kuryerlarni kuzatish servisini qurishdan oldin uni qog'oz ustida o'lchab chiqing: foydalanuvchilardan soniyasiga so'rovlarga, so'rovlardan kunlik baytlarga, baytlardan disk, tarmoq va serverlarga. Taxminiy sonlar, bir necha daqiqa — va qimmat xatolar birinchi kod qatoridan oldin ko'rinadi.
Nimani o'rganasiz
- «Nechta foydalanuvchi» ni soniyasiga so'rovlarga aylantirish: o'rtacha va eng yuqori
- Bitta qator hajmidan kunlik va yillik xotirani hisoblash
- Tarmoqni yeydigan narsani prod'ga chiqmasdan oldin topish
- Eslab qolishga arziydigan kechikish sonlari va serverlarni zaxira bilan sanash
Diagramma kod sifatida
Darsdagi yakuniy sxemani matn ko'rinishida oling va Jira, GitLab, GitHub, Notion yoki hujjatga qo'ying: Mermaid u yerlarda o'zi chiziladi. D2 va PlantUML (Confluence, IntelliJ) uchun alohida variantlar bor.
Mermaid: sxema
flowchart LR
n_couriers(["Kuryer ilovasi"])
n_api["Kuzatuv API"]
n_db[("Baza")]
n_customers(["Mijoz ilovasi"])
n_archive[("Arxiv")]
n_cdn[/"CDN"\]
n_couriers --> n_api
n_api --> n_db
n_customers --> n_api
n_api -.-> n_customers
n_db --> n_archive
n_customers --> n_cdnMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_couriers as Kuryer ilovasi
participant n_api as Kuzatuv API
participant n_customers as Mijoz ilovasi
participant n_db as Baza
participant n_archive as Arxiv
participant n_cdn as CDN
Note over n_couriers,n_api: Foydalanuvchilardan boshlang
n_couriers->>n_api: POST /v1/pings HTTP/1.1
n_api-->>n_couriers: HTTP/1.1 204 No Content
Note over n_customers,n_api: O'quvchilarni qo'shing
n_customers->>n_api: GET /v1/orders/o_42/track HTTP/1.1
n_api-->>n_customers: HTTP/1.1 200 OK
Note over n_api,n_db: Bitta ping qancha joy oladi?
n_api->>n_db: SELECT avg(pg_column_size(p.*)) AS row_bytes
n_db-->>n_api: row_bytes = 61
Note over n_api,n_db: Hammasini bir yil saqlash
n_api->>n_db: SELECT pg_size_pretty(
n_db-->>n_api: 6.3 TB
Note over n_db,n_archive: 7 kun bazada, qolgani arxivda
n_db->>n_archive: PUT /pings/2026-11-10.parquet HTTP/1.1
n_archive-->>n_db: HTTP/1.1 200 OK
Note over n_customers,n_api: Og'ir qism — xarita
n_customers->>n_api: GET /tiles/14/10712/6131.png HTTP/1.1
n_api-->>n_customers: HTTP/1.1 200 OK
Note over n_customers,n_cdn: Tile'larni CDN'dan berish
n_customers->>n_cdn: GET /tiles/14/10712/6131.png HTTP/1.1
n_cdn-->>n_customers: HTTP/1.1 200 OK
Note over n_couriers,n_api: Nechta app server kerak?
n_couriers->>n_api: load test: 1 instance, 4 vCPUD2
direction: right
n_couriers: "Kuryer ilovasi" {
shape: rectangle
}
n_api: "Kuzatuv API" {
shape: rectangle
}
n_db: "Baza" {
shape: cylinder
}
n_customers: "Mijoz ilovasi" {
shape: rectangle
}
n_archive: "Arxiv" {
shape: stored_data
}
n_cdn: "CDN" {
shape: oval
}
n_couriers -> n_api
n_api -> n_db
n_customers -> n_api
n_api -> n_customers {
style.stroke-dash: 3
}
n_db -> n_archive
n_customers -> n_cdnPlantUML: so'rovlar ketma-ketligi
@startuml
participant "Kuryer ilovasi" as n_couriers
participant "Kuzatuv API" as n_api
participant "Mijoz ilovasi" as n_customers
database "Baza" as n_db
database "Arxiv" as n_archive
participant "CDN" as n_cdn
note over n_couriers, n_api : Foydalanuvchilardan boshlang
n_couriers -> n_api : POST /v1/pings HTTP/1.1
n_api --> n_couriers : HTTP/1.1 204 No Content
note over n_customers, n_api : O'quvchilarni qo'shing
n_customers -> n_api : GET /v1/orders/o_42/track HTTP/1.1
n_api --> n_customers : HTTP/1.1 200 OK
note over n_api, n_db : Bitta ping qancha joy oladi?
n_api -> n_db : SELECT avg(pg_column_size(p.*)) AS row_bytes
n_db --> n_api : row_bytes = 61
note over n_api, n_db : Hammasini bir yil saqlash
n_api -> n_db : SELECT pg_size_pretty(
n_db --> n_api : 6.3 TB
note over n_db, n_archive : 7 kun bazada, qolgani arxivda
n_db -> n_archive : PUT /pings/2026-11-10.parquet HTTP/1.1
n_archive --> n_db : HTTP/1.1 200 OK
note over n_customers, n_api : Og'ir qism — xarita
n_customers -> n_api : GET /tiles/14/10712/6131.png HTTP/1.1
n_api --> n_customers : HTTP/1.1 200 OK
note over n_customers, n_cdn : Tile'larni CDN'dan berish
n_customers -> n_cdn : GET /tiles/14/10712/6131.png HTTP/1.1
n_cdn --> n_customers : HTTP/1.1 200 OK
note over n_couriers, n_api : Nechta app server kerak?
n_couriers -> n_api : load test: 1 instance, 4 vCPU
@endumlPlantUML: komponentlar
@startuml
left to right direction
agent "Kuryer ilovasi" as n_couriers
component "Kuzatuv API" as n_api
database "Baza" as n_db
agent "Mijoz ilovasi" as n_customers
storage "Arxiv" as n_archive
frame "CDN" as n_cdn
n_couriers --> n_api
n_api --> n_db
n_customers --> n_api
n_api ..> n_customers
n_db --> n_archive
n_customers --> n_cdn
@endumlXulosa
Qog'oz ustidagi hisob — oddiy ko'paytirishlar zanjiri: foydalanuvchilar → soniyasiga so'rovlar → kunlik baytlar → disk, tarmoq va serverlar.
1) Har bir farazni yozing va o'rtachaga emas, cho'qqiga rejalashtiring. 2) Bir kun ~100 000 soniya. 3) Ma'lumot qancha yashashi kerakligini so'rang. 4) Har bir endpoint uchun baytni tezlikka ko'paytiring. 5) Kechikish nisbatlarini yodda tuting: xotira, SSD, data markaz, qit'a.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| Eng yuqori so'rovlar | 2 000/s | 2 300/s |
| Baza hajmi | 17 GB | 120 GB |
| API chiquvchi trafigi, soniyasiga | 0,3 MB | 0,3 MB |
| App serverlar | 4 | 4 |
Qadamlar
- Holat Foydalanuvchilardan boshlang
Eng band soatda 20 000 kuryer ishda.
- Holat O'quvchilarni qo'shing
Kuniga 300 000 buyurtma, har bir mijoz kuzatuvni taxminan 20 marta ochadi: kuniga 6 million o'qish.
- Holat Bitta ping qancha joy oladi?
Qator hajmini taxmin qilmang, bazadan so'rang.
- Muammo Hammasini bir yil saqlash
Kuniga 17 GB × 365 ≈ 6,3 TB, 63 milliard qator.
- Yechim 7 kun bazada, qolgani arxivda
Baza faqat oxirgi 7 kunni saqlaydi: 7 × 17 ≈ 120 GB, bu oddiy bitta serverga sig'adi.
- Muammo Og'ir qism — xarita
Kuzatuv ekrani xarita ko'rsatadi, xarita tile'larini esa API o'zi beradi.
- Yechim Tile'larni CDN'dan berish
Tile'lar hamma uchun bir xil va kam o'zgaradi, shuning uchun CDN ularni foydalanuvchilarga yaqin joyda keshlay oladi.
- Holat Eslab qolishga arziydigan kechikishlar
Xotira: ~100 ns.
- Holat Nechta app server kerak?
Taxmin qilmang, o'lchang: yuklama testi 4 vCPU li bitta instance soniyasiga 800 so'rovni 61% CPU da va yaxshi p99 bilan ko'tarishini ko'rsatadi.
- Xulosa Xulosa
Qog'oz ustidagi hisob — oddiy ko'paytirishlar zanjiri: foydalanuvchilar → soniyasiga so'rovlar → kunlik baytlar → disk, tarmoq va serverlar.
Atamalar
- Qog'oz ustidagi hisob (napkin math)
- Tizim hajmini oddiy ko'paytirishlar zanjiri bilan taxmin qilish: foydalanuvchilar, soniyasiga so'rovlar, kunlik baytlar, keyin disk, tarmoq va serverlar. Har bir faraz yoziladi, o'rtachaga emas, cho'qqiga rejalashtiriladi.