laravel-performance
Skill0 starsChanged 29 days agoMITView on GitHub
Optimisation des performances Laravel 13. Cache, query optimization, profiling, lazy loading, Pulse. Utiliser quand on optimise une app lente, on debug des requêtes lentes, on configure le cache, ou on profile.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- stoffl6781/claude-skilltheir own version, first seen Apr 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- stoffl6781/claude-skill★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/laravel-core/templates/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- dokploy-deploySkill
- laravel-adminSkill
- laravel-aiSkill
- laravel-apiSkill
- laravel-coreSkill
- laravel-deploySkill
- laravel-inertiaSkill
- laravel-livewireSkill
- laravel-mcpSkill
- laravel-microserviceSkill
- laravel-multi-tenancySkill
- laravel-nuxtSkill
- laravel-queueSkill
- laravel-securitySkill
- laravel-testingSkill
- laravel-websocketSkill
- nuxt-coreSkill
- nuxt-uiSkill
- pestSkill
- project-definerSkill
- scribeSkill
- searxng-mcpSkill
- sentrySkill
- skill-creatorSkill
- skill-health-checkerSkill
- spatie-query-builderSkill
The file
Files
Laravel Performance — Performance Laravel 13
Tu es un expert en performance Laravel 13. Ton rôle est d'optimiser les applications pour la vitesse et l'efficacité.
Quand utiliser
- Application lente
- Requêtes DB lentes (N+1)
- Configuration du cache
- Profiling des performances
- Optimisation pour la production
Patterns de performance
Cache
<?php
use Illuminate\Support\Facades\Cache;
// Cache simple
$posts = Cache::remember('posts.all', now()->addMinutes(30), function () {
return Post::all();
});
// Cache avec tags
Cache::tags(['posts', 'home'])->put('featured', $posts, 3600);
// Étendre le TTL sans re-stocker (Laravel 13)
Cache::touch('posts.all', 1800);
// Cache memoization (même requête = même réponse dans la même requête)
$posts = Cache::memo()->remember('posts.all', 300, fn () => Post::all());Query Optimization
<?php
// ❌ Mal : N+1 query
$posts = Post::all();
foreach ($posts as $post) {
echo $post->user->name; // Query supplémentaire !
}
// ✅ Bon : Eager loading
$posts = Post::with('user')->get();
// ✅ Bon : Select spécifique
$posts = Post::select('id', 'title', 'user_id')->with('user:id,name')->get();
// ✅ Bon : Cursor pour les gros datasets
$posts = Post::cursor();
foreach ($posts as $post) {
// Traitement un par un, pas de charge mémoire
}
// ✅ Bon : Chunking pour les opérations en masse
Post::chunk(100, function ($posts) {
foreach ($posts as $post) {
// Traitement par lots
}
});
// ✅ Bon : Détecter le N+1 en dev
Model::preventLazyLoading(!app()->isProduction());Indexing
<?php
// ✅ Bon : Index sur les colonnes fréquemment query
Schema::table('posts', function (Blueprint $table) {
$table->index('user_id');
$table->index(['status', 'created_at']);
$table->fullText('content'); // Pour la recherche full-text
});
// ✅ Bon : Composite index
$table->index(['user_id', 'status', 'created_at']);Pagination
<?php
// ✅ Bon : Toujours paginer les listes
$posts = Post::paginate(20);
// ✅ Bon : Cursor pagination pour les gros datasets
$posts = Post::cursorPaginate(50);
// ✅ Bon : Simple pour les APIs
$posts = Post::simplePaginate(20);Lazy Loading vs Eager Loading
<?php
// Lazy loading (par défaut) — charge à l'accès
$user->posts; // Charge ici
// Eager loading — charge en avance
$users = User::with('posts')->get(); // Tout charge d'un coup
// Lazy eager loading — charge à la demande mais en batch
$users = User::all();
$users->load('posts'); // Charge tous les posts d'un coupProfiling
<?php
// Laravel Telescope (dev)
composer require laravel/telelescope --dev
php artisan telescope:install
// Laravel Pulse (production)
composer require laravel/pulse
php artisan pulse:install
// Debugbar (dev)
composer require barryvdh/laravel-debugbar --devQueue pour les tâches lourdes
<?php
// ✅ Bon : Job pour les tâches longues
class ProcessCsv implements ShouldQueue
{
use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;
public int $timeout = 300;
public int $tries = 3;
public function handle(): void
{
// Traitement long...
}
}
// Dispatch asynchrone
ProcessCsv::dispatch($file);CDN et Assets
// ✅ Bon : CDN pour les assets statiques
APP_URL=https://example.com
ASSET_URL=https://cdn.example.com
// ✅ Bon : Mix/Vite pour le versioning
// vite.config.js
import { defineConfig } from 'vite';
export default defineConfig({
build: {
rollupOptions: {
output: {
manualChunks: {
vendor: ['axios', 'lodash'],
},
},
},
},
});Bonnes pratiques
- Cache les queries fréquentes — Avec
Cache::remember()ou tags - Éviter le N+1 —
with()oupreventLazyLoading() - Toujours paginer —
paginate()oucursorPaginate() - Indexer les colonnes query — Composite index quand nécessaire
- Utiliser des jobs — Pour les tâches longues
- CDN pour les assets — Réduire la charge sur le serveur
- Monitoring — Pulse en production
- Optimiser les images — Compression, lazy loading
- HTTP caching — Cache-Control headers
- Database optimization —
EXPLAINpour analyser les requêtes
Validation
- Pas de N+1 queries (
php artisan pulse:check) - Cache configuré pour les données fréquentes
- Toutes les listes paginées
- Index sur les colonnes query
- Jobs pour les tâches longues
- Assets versionnés et CDN
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

