13-amaliy mashg‘ulot · 13-mavzu · 2 soat · Korxona ilovalarini dasturlash
Jamoa loyihasi (OmborPro) bosqichi, 5 ta amaliy PHP topshiriq va 3 ta ma’ruzadagi mashq. Yo‘riqnoma bo‘yicha loyihada ishlang, havolani topshiring va PHP topshiriqlarni yeching — server yashirin testlar bilan tekshiradi, o‘qituvchi baho qo‘yadi.
EXPLAIN ANALYZE bilan isbotlashnirequest_id, /up va /health endpointlarinidocs/performance.md)Katta test ma’lumotlari · Debugbar · eager loading · so‘rovlar soni testi
Unumdorlik muammolari faqat katta ma’lumotda ko‘rinadi, shuning uchun birinchi qadam — realistik hajmdagi test ma’lumotlari. Alohida PerformanceSeeder yarating: 2 000 ta mahsulot, 300 ta kontragent, 3 ta ombor, 20 000 ta buyurtma (har birida 1–5 pozitsiya), 50 000 ta ombor harakati. Factory’lardan foydalaning (Order::factory()->count(...)->has(OrderItem::factory()->count(3), 'items')), katta hajmda esa insert() bilan 1 000 talik bo‘laklarda yozing — aks holda seeder o‘zi soatlab ishlaydi. Bu seeder faqat lokal va staging uchun, productionga ishga tushirilmaydi.
Keyin barryvdh/laravel-debugbar ni --dev bilan o‘rnating va asosiy sahifalarni birma-bir oching: buyurtmalar ro‘yxati, buyurtma kartasi, mahsulotlar (ProductTable Livewire komponenti), hisob-fakturalar, dashboard, API GET /api/v1/products. Har bir sahifa uchun jadvalga yozing: so‘rovlar soni, takroriy so‘rovlar, sahifa vaqti, yuklangan modellar soni. API uchun Debugbar ko‘rinmaydi — Telescope yoki DB::enableQueryLog() bilan test orqali o‘lchang. Bu boshlang‘ich nuqta (baseline): keyingi barcha o‘zgarishlar shu raqamlar bilan solishtiriladi.
Takroriy so‘rovlar topilgan joylarda eager loading qo‘llang: controller’da with([...]), sanoq va yig‘indi uchun withCount() / withSum(), API resurslarida whenLoaded() bilan faqat yuklangan munosabatni chiqarish. AppServiceProvider da Model::preventLazyLoading(! $this->app->isProduction()) ni yoqing va barcha sahifalarni qayta oching — qolgan lazy loading joylari istisno bilan ko‘rinadi. Oxirida eng muhim sahifalar uchun so‘rovlar soni testi yozing: 5 ta va 30 ta buyurtma bilan so‘rovlar soni bir xil bo‘lishi kerak. Bunday test kelajakda kimdir Blade’ga yangi munosabat qo‘shib N+1 ni qaytarsa, CI’da darhol yiqiladi.
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
migrate:fresh — faqat lokal bazada! barcha jadvallarni o‘chirib qayta yaratadi--seeder= — faqat katta hajmli seeder ishga tushadi->each->counterparty — har bir buyurtma uchun lazy so‘rov — 51 ta| 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 |
<?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
$count(5) vs $count(25) — N+1 bo‘lsa, ikkinchi son katta chiqadi va test yiqiladiDB::flushQueryLog() — ma’lumot tayyorlash so‘rovlari hisobga kirmaydihasItems(3) — factory’ning sehrli has{Munosabat} metodi: har buyurtmaga 3 ta pozitsiyaSo‘rovlarni yig‘ish · indeks migratsiyasi · EXPLAIN ANALYZE · Redis kesh va invalidation
Indekslarni taxmin bilan emas, haqiqiy so‘rovlar ro‘yxati asosida qo‘ying. Debugbar yoki Telescope’dan eng sekin va eng ko‘p takrorlanadigan 5–7 ta so‘rovni yozib oling (->toRawSql() bilan aniq SQL). Har biri uchun psql’da EXPLAIN (ANALYZE, BUFFERS) ni bajaring va natijani saqlang: reja turi, Rows Removed by Filter, Execution Time. OmborPro uchun tipik nomzodlar: orders(status, created_at), orders(counterparty_id), order_items(order_id), stock_movements(product_id, created_at), invoices(status, due_at), payments(invoice_id). unique cheklovlar (products.sku, stocks(warehouse_id, product_id), payments.external_id) allaqachon indeksga ega — ularni takrorlamang.
Indekslar alohida migratsiyada qo‘shiladi (add_performance_indexes), down() da esa dropIndex([...]) bilan olib tashlanadi. Migratsiyadan keyin ANALYZE orders; (PostgreSQL statistikasini yangilash) va xuddi shu EXPLAIN larni qayta bajaring. Natija Index Scan yoki Bitmap Index Scan bo‘lishi, Execution Time keskin kamayishi kerak. Agar planner baribir Seq Scan tanlasa — sababini tahlil qiling: jadval kichikmi, shart selektivmi, ustunga funksiya qo‘llanmaganmi? Hisobotga ikkala rejani ham qo‘shing.
Dashboard va oylik hisobotlar kabi og‘ir agregatsiyalarni ReportService da Redis kesh bilan o‘rang. .env da CACHE_STORE=redis, kalitlarga barcha parametrlarni kiriting (oy, ombor, format versiyasi), teglar bilan guruhlang (reports, warehouse:{id}), TTL qo‘ying (5–15 daqiqa). Invalidation uchun OrderConfirmed va to‘lov qabul qilinishi hodisalariga listener yozing. Kesh ishlashini isbotlang: birinchi so‘rov MISS (vaqt va SQL soni), ikkinchisi HIT (0 ta SQL), buyurtma tasdiqlangandan keyin yana MISS. Bu ketma-ketlikni Pest testi bilan ham tekshirish mumkin: Cache::tags(['reports'])->has($key).
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([...]) — har bir indeks — sekin so‘rovlar ro‘yxatidagi aniq so‘rov uchundropIndex([...]) — ustunlar massivi bo‘yicha Laravel indeks nomini o‘zi tiklaydidown() — namuna qisqartirilgan: har bir index() uchun dropIndex() yozing-- 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
oldin/keyin — ikkala reja ham docs/performance.md ga qo‘shiladipublic 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 qoladinow()->addMinutes(5) — invalidation unutilsa ham ma’lumot 5 daqiqadan ortiq eskirmaydiwarehouse:{id} — faqat o‘zgargan omborning keshi tozalanadiJSON kanal va request_id · /up va /health · Sentry (ixtiyoriy) · docs/performance.md
config/logging.php ga JSON kanal qo‘shing va .env da LOG_STACK=daily,json qiling. AssignRequestId middleware’i har bir so‘rovga request_id beradi (Context::add) va uni X-Request-Id javob sarlavhasida qaytaradi. Biznes hodisalarini strukturali loglang: order.confirmed, stock.reserved, invoice.issued, payment.received, import.finished — har birida identifikatorlar va summalar kontekstda. Maxfiy maydonlar (parol, token, karta) logga tushmasligini tekshiring: storage/logs dagi faylni grep password bilan qidiring — natija bo‘sh bo‘lishi kerak.
bootstrap/app.php da health: '/up' borligini tekshiring va DiagnosingHealth listener’i bilan baza va Redis tekshiruvini qo‘shing. Alohida /health marshruti JSON qaytarsin: database, redis, queue (navbat uzunligi) tekshiruvlari, har biri ok va ms bilan; muhim qism ishlamasa 503. Sinab ko‘ring: docker compose stop db dan keyin /up 500, /health 503 qaytarishi kerak; docker compose start db dan keyin yana 200. Ixtiyoriy (qo‘shimcha ball): Sentry yoki GlitchTip ulang, php artisan sentry:test bilan test hodisasini yuboring va request_id ni Sentry tegi sifatida qo‘shing.
Yakunda docs/performance.md hisobotini yozing — bu amaliy mashg‘ulotning asosiy natijasi. Tuzilmasi: test muhiti va ma’lumot hajmi; o‘lchash usuli; jadval “sahifa → so‘rovlar va vaqt oldin/keyin”; har bir indeks uchun EXPLAIN oldin/keyin; kesh kalitlari ro‘yxati, TTL va invalidation hodisasi; loglash va health endpoint tavsifi; qolgan muammolar va keyingi qadamlar. Hisobotdagi har bir raqam takrorlanadigan bo‘lsin: boshqa jamoa a’zosi seeder va buyruqlarni ishga tushirib, xuddi shunday natijani olishi kerak.
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
/up → 500 — DiagnosingHealth listener’idagi DB::select istisno tashladi/health → 503 — muhim tekshiruv (database) ishlamadi — failDB::getQueryLog(), EXPLAIN (ANALYZE, BUFFERS), 5 marta o‘lchab medianarequest_id, /up va /health javoblari, Sentry (bo‘lsa)Natija: asosiy sahifalarda N+1 muammolari bartaraf etilgan, haqiqiy so‘rovlar uchun indekslar qo‘shilgan, hisobotlar Redis’da keshlanadi, JSON loglar va health endpoint ishlaydi; “oldin/keyin” raqamlari bilan unumdorlik hisoboti tayyor.
Baholash mezonlariPerformanceSeeder mavjud va kamida 10 000 ta buyurtma yaratadi; Debugbar faqat require-dev da.Model::preventLazyLoading() dev muhitda yoqilgan.EXPLAIN ANALYZE oldin/keyin hisobotda bor.request_id ishlaydi; loglarda parol, token va karta raqami yo‘q./up va /health ishlaydi: baza to‘xtatilganda mos ravishda 500 va 503 qaytaradi.docs/performance.md — o‘lchov jadvali, rejalar, kesh strategiyasi va qolgan muammolar bilan.📤 GitHub’dagi 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.
Qanday ishlaydi. Chapdan topshiriqni tanlang, shartni o‘qing va shartdagi imzo bo‘yicha sof PHP funksiya yoki sinf yozing (Laravelsiz). ▶ Sinab ko‘rish — pastdagi chaqiruv ifodasini kodingiz bilan bajaradi (baholanmaydi). ✓ Topshirish — server kodni namunaviy va yashirin testlar bilan tekshiradi; natija o‘qituvchiga ko‘rinadi.