Profillash, indekslar va keshlash
Amaliy mashg‘ulot oxirida siz quyidagilarni bajara olasiz...
EXPLAIN ANALYZE bilan isbotlashnirequest_id, /up va /health endpointlarinidocs/performance.md)Qanday bajariladi va qanday baholanadi?
Ish tartibi
- Saytga login va parolingiz bilan kiring: emro.uz/korxona/kirish.html
- 13-amaliy sahifasini oching (oxirgi slayddagi QR kod).
- Yo‘riqnoma bo‘yicha jamoa loyihasida bosqichni bajaring, commit va push qiling.
- PHP topshiriqlarni yeching: ▶ Sinab ko‘rish → ✓ Topshirish (yashirin testlar).
- Loyiha havolasini (GitHub repo, PR yoki tag) topshiring — o‘qituvchi baho qo‘yadi.
Baholash mezonlari
- Natija — loyiha bosqichi mezonlar ro‘yxati bo‘yicha bajarilgan.
- Topshiriqlar — PHP topshiriqlar testlardan o‘tgan.
- Kod sifati — tushunarli nomlar, PSR-12, kichik va mazmunli commitlar.
- Jamoaviy hissa — har bir a’zo o‘z qismini tushuntira oladi; ko‘chirilgan ish baholanmaydi.
- Muddat — muddatdan keyin topshirilgan ish “kechikkan” deb belgilanadi.
1-bosqich: profillash va N+1 ni bartaraf etish
Ma’lumot va profiler
composer require barryvdh/laravel-debugbar --dev php artisan make:seeder PerformanceSeeder php artisan migrate:fresh --seed --seeder=PerformanceSeeder # so'rovlar sonini tez tekshirish (tinker) php artisan tinker >>> DB::enableQueryLog(); >>> Order::latest()->take(50)->get()->each->counterparty; >>> count(DB::getQueryLog());
Database\Seeders\PerformanceSeeder ........... 48s DONE = 51
Boshlang‘ich nuqta (baseline) — namuna
| Sahifa | So‘rovlar (oldin → keyin) | Vaqt (oldin → keyin) | Nima qilindi |
|---|---|---|---|
/orders (50 ta) | 103 → 6 | 2,4 s → 180 ms | with(['counterparty', 'warehouse']), withCount('items') |
/orders/{id} | 38 → 4 | 420 ms → 60 ms | load('items.product', 'invoice.payments') |
ProductTable (Livewire) | 62 → 3 | 900 ms → 110 ms | with('category'), stocks yig‘indisi withSum() |
GET /api/v1/products | 41 → 3 | 350 ms → 70 ms | with() + whenLoaded() resursda |
| Dashboard | 12 → 12 | 3,1 s → 3,1 s | N+1 emas — og‘ir agregatsiya: 2-bosqichda kesh |
So‘rovlar soni buyurtmalar soniga bog‘liq emas
<?php use App\Models\Order; use App\Models\User; use Illuminate\Support\Facades\DB; it('orders sahifasida N+1 yo‘q', function () { $this->actingAs(User::factory()->create()); $count = function (int $n): int { Order::factory()->count($n)->hasItems(3)->create(); DB::flushQueryLog(); DB::enableQueryLog(); $this->get('/orders')->assertOk(); return count(DB::getQueryLog()); }; expect($count(5))->toBe($count(25)); });
PASS Tests\Feature\OrdersPerformanceTest ✓ orders sahifasida N+1 yo‘q 0.84s
has{Munosabat} metodi: har buyurtmaga 3 ta pozitsiya2-bosqich: indekslar va hisobotlarni keshlash
add_performance_indexes
public function up(): void { Schema::table('orders', function (Blueprint $table) { $table->index(['status', 'created_at']); $table->index('counterparty_id'); }); Schema::table('stock_movements', function (Blueprint $table) { $table->index(['product_id', 'created_at']); }); Schema::table('invoices', function (Blueprint $table) { $table->index(['status', 'due_at']); }); } public function down(): void { Schema::table('orders', fn (Blueprint $t) => $t->dropIndex( ['status', 'created_at'])); }
INFO Running migrations. 2026_10_27_120000_add_performance_indexes ...... 1.2s DONE
index() uchun dropIndex() yozingEXPLAIN (ANALYZE, BUFFERS): oldin va keyin
-- muddati o'tgan to'lanmagan hisob-fakturalar EXPLAIN (ANALYZE, BUFFERS) SELECT id, number, total, paid_amount FROM invoices WHERE status = 'unpaid' AND due_at < '2026-10-27' ORDER BY due_at LIMIT 100; -- migratsiyadan keyin statistikani yangilash ANALYZE invoices;
-- oldin: Seq Scan on invoices ... Rows Removed by Filter: 118930 -- Buffers: shared hit=2210 Execution Time: 28.7 ms -- keyin: Index Scan using invoices_status_due_at_index on invoices -- Buffers: shared hit=9 Execution Time: 0.3 ms
docs/performance.md ga qo‘shiladiDashboard keshi va invalidation
public function dashboard(int $whId): array { return Cache::tags(['reports', "warehouse:{$whId}"])->remember( "report:dashboard:v1:wh={$whId}", now()->addMinutes(5), fn () => [ 'today_orders' => $this->todayOrders($whId), 'low_stock' => $this->lowStockCount($whId), 'unpaid_total' => $this->unpaidTotal(), ], ); } // app/Listeners/FlushReportCache.php public function handle(OrderConfirmed $event): void { Cache::tags(["warehouse:{$event->order->warehouse_id}"])->flush(); }
GET /dashboard 1-marta: MISS 12 SQL 3,1 s GET /dashboard 2-marta: HIT 0 SQL 95 ms OrderConfirmed → flush → 3-marta: MISS
v2 — eski kesh avtomatik ishlatilmay qoladi3-bosqich: loglash, health endpoint va unumdorlik hisoboti
Health endpointni tekshirish
curl -i https://omborpro.test/up curl -s https://omborpro.test/health | jq .status docker compose stop db curl -s -o /dev/null -w "%{http_code}\n" https://omborpro.test/up curl -s -o /dev/null -w "%{http_code}\n" https://omborpro.test/health docker compose start db # loglarda parol yo'qligini tekshirish grep -ri "password" storage/logs/ || echo 'toza'
HTTP/1.1 200 OK "ok" 500 503 toza
DiagnosingHealth listener’idagi DB::select istisno tashladidatabase) ishlamadi — faildocs/performance.md tuzilmasi
Muhit
Usul
DB::getQueryLog(), EXPLAIN (ANALYZE, BUFFERS), 5 marta o‘lchab medianaN+1
Indekslar
Kesh
Kuzatuvchanlik
request_id, /up va /health javoblari, Sentry (bo‘lsa)Natija va topshirish
Baholash mezonlari
PerformanceSeedermavjud va kamida 10 000 ta buyurtma yaratadi; Debugbar faqatrequire-devda.- Kamida 3 ta sahifa yoki endpoint uchun N+1 bartaraf etilgan;
Model::preventLazyLoading()dev muhitda yoqilgan. - So‘rovlar soni buyurtmalar soniga bog‘liq emasligini tekshiruvchi kamida bitta Pest testi CI’da o‘tadi.
- Alohida migratsiyada kamida 3 ta indeks qo‘shilgan, har biri uchun
EXPLAIN ANALYZEoldin/keyin hisobotda bor. - Kamida bitta hisobot Redis’da teglar bilan keshlanadi; kalitda barcha parametrlar; hodisa bo‘yicha invalidation ishlaydi.
- JSON log kanali va
request_idishlaydi; loglarda parol, token va karta raqami yo‘q. /upva/healthishlaydi: baza to‘xtatilganda mos ravishda 500 va 503 qaytaradi.docs/performance.md— o‘lchov jadvali, rejalar, kesh strategiyasi va qolgan muammolar bilan.
perf branch’idan main ga Pull Request havolasini topshiring: PR tavsifida docs/performance.md ga havola, Debugbar skrinshotlari (oldin/keyin) va /health javobi bo‘lsin.4-topshiriq: Apdex: foydalanuvchi qoniqishi
Javob vaqtlari $ms (millisekund) va maqsad chegarasi $t berilgan. Apdex = (qoniqarli + chidasa bo‘ladigan / 2) / jami. Qoniqarli: vaqt ≤ T; chidasa bo‘ladigan: T < vaqt ≤ 4T; qolganlari — norozi. Natija round(..., 2). Massiv bo‘sh yoki $t ≤ 0 bo‘lsa — InvalidArgumentException.
Imzo: function apdex(array $ms, int $t): float
Qaytaradi: float — 0 dan 1 gacha, 2 xona aniqlikda.
apdex([100, 200, 300, 1500, 2500], 500)
0.7
5-topshiriq: Strukturali log yozuvi va niqoblash
Log darajasi $daraja (katta-kichik harf farqsiz; ruxsat etilgan: debug, info, notice, warning, error, critical, alert, emergency), xabar $xabar va kontekst $kontekst berilgan. Kontekstni rekursiv niqoblang: kaliti (katta-kichik harf farqsiz) password, token, api_key, card_number, secret bo‘lgan qiymat (massiv bo‘lsa ham) *** ga almashtiriladi; kaliti phone bo‘lgan satr 4 belgidan uzun bo‘lsa, oxirgi 4 belgidan boshqasi * bilan almashtiriladi; ichki massivlar ham shu qoidalar bilan tekshiriladi. Noma’lum daraja yoki bo‘sh (faqat bo‘sh joylardan iborat) xabar — InvalidArgumentException.
Imzo: function log_yozuvi(string $daraja, string $xabar, array $kontekst): array
Qaytaradi: ['level' => KATTA_HARFDA, 'message' => string, 'context' => array] — kalitlar shu tartibda, kontekst kalitlari tartibi o‘zgarmaydi.
log_yozuvi('warning', 'payment.failed', ['invoice_id' => 45, 'token' => 'tok_1']){"level":"WARNING","message":"payment.failed","context":{"invoice_id":45,"token":"***"}}6-topshiriq: Health check holatini hisoblash
Tekshiruvlar ro‘yxati berilgan: har biri ['name' => string, 'ok' => bool, 'critical' => bool, 'ms' => int]. failed — ok = false bo‘lgan tekshiruv nomlari, slow — ok = true, lekin ms > $sekinMs bo‘lganlar (ikkalasi kirish tartibida). Holat: kamida bitta muhim (critical) tekshiruv muvaffaqiyatsiz bo‘lsa — fail; aks holda failed yoki slow bo‘sh bo‘lmasa — degraded; qolgan holatda — ok. HTTP kod: fail → 503, boshqalari → 200. Ro‘yxat bo‘sh bo‘lsa — DomainException.
Imzo: function health_holati(array $tekshiruvlar, int $sekinMs = 1000): array
Qaytaradi: ['status' => string, 'http' => int, 'failed' => array, 'slow' => array] — kalitlar shu tartibda.
health_holati([['name' => 'db', 'ok' => true, 'critical' => true, 'ms' => 4], ['name' => 'queue', 'ok' => false, 'critical' => false, 'ms' => 2]])
{"status":"degraded","http":200,"failed":["queue"],"slow":[]}7-topshiriq: Teglar va TTL bilan kesh
Redis keshining soddalashtirilgan modelini yozing. put($key, $value, $ttl, $tags, $now) — qiymatni $now + $ttl gacha saqlaydi ($ttl ≤ 0 — InvalidArgumentException); get($key, $now) — qiymat yoki muddati o‘tgan/yo‘q bo‘lsa null ($now ≥ muddat — eskirgan); remember($key, $ttl, $tags, $now, $fn) — yaroqli qiymat bo‘lsa uni qaytaradi (hit), aks holda $fn() ni chaqirib saqlaydi (miss); flushTag($tag) — shu tegli barcha saqlangan yozuvlarni (muddatidan qat’i nazar) o‘chiradi va ularning sonini qaytaradi; stats() — faqat remember chaqiruvlari bo‘yicha hisob.
Imzo: final class TagCache
Qaytaradi: get/remember — saqlangan qiymat; flushTag — int; stats() — ['hits' => int, 'misses' => int].
(function () { $c = new TagCache(); $f = fn () => 2480000; $a = $c->remember('r:10', 600, ['reports'], 0, $f); $b = $c->remember('r:10', 600, ['reports'], 100, $f); return [$a, $b, $c->stats()]; })()[2480000,2480000,{"hits":1,"misses":1}]8-topshiriq: Takroriy so‘rovlarni aniqlash (N+1 detektori)
So‘rovlar logi $sorovlar (SQL satrlar) berilgan. Har bir so‘rovni normallashtiring: 1) bir tirnoqli satr literallari (ichidagi '' bilan) → ?; 2) alohida so‘z bo‘lgan sonlar (butun yoki o‘nlik, masalan 5, 12.50) → ?; 3) in (?, ?, ...) ro‘yxati (katta-kichik harf farqsiz in) → in (?); 4) ketma-ket bo‘sh joylar bitta probelga, chetlari kesiladi. Bir xil normallashgan so‘rovlarni sanang va soni $chegara dan kichik bo‘lmaganlarini qaytaring: soni bo‘yicha kamayish, teng bo‘lsa SQL bo‘yicha alifbo tartibida. $chegara < 2 — InvalidArgumentException.
Imzo: function takroriy_sorovlar(array $sorovlar, int $chegara): array
Qaytaradi: [['sql' => string, 'count' => int], ...] — bo‘sh bo‘lishi mumkin.
takroriy_sorovlar(['select * from orders limit 50', 'select * from counterparties where id = 3', 'select * from counterparties where id = 7', 'select * from counterparties where id = 12'], 3)
[{"sql":"select * from counterparties where id = ?","count":3}]