Weave Code
Profiler Laravel Package
yiisoft/profiler
Yii Profiler is a lightweight profiling component for Yii3 applications. It collects timing and memory usage data, supports custom checkpoints, and helps developers identify performance bottlenecks during development.
The package provides an ability to record performance profiles.
Frequently asked questions about Profiler
- What is yiisoft/profiler and what does it do?
- yiisoft/profiler is a lightweight profiling component for Yii3 applications. It records timing and memory usage data, supports custom checkpoints, and helps developers identify performance bottlenecks during development. It is not a Laravel-native observability package.
- Is yiisoft/profiler a Laravel package?
- No, yiisoft/profiler belongs to the Yii3 ecosystem and is not built specifically for Laravel. You could wrap it behind a Laravel service provider, middleware, events, and job or command hooks, but that integration would be custom work. Laravel already offers stronger default options such as Telescope, Clockwork, Debugbar, Xdebug, and APM tools.
- How do I install yiisoft/profiler in a Laravel app?
- Composer installation is likely straightforward, but the package does not ship Laravel service providers, configuration, middleware, or storage/export integration. You would need to build an adapter layer and decide how profiles are enabled, captured, stored, and visualized. Pin the exact package version and test its Composer constraints against your Laravel, Symfony, PSR, and observability dependencies.
- Can I use yiisoft/profiler without the Yii container or runtime?
- That is a key due-diligence question and should be proven with a time-boxed spike before adoption. The profiler core may be usable standalone, but feasibility depends on whether it makes Yii-specific assumptions about its container, middleware, or configuration conventions. Do not assume it will drop cleanly into Laravel without an adapter.
- Which Laravel and PHP versions does yiisoft/profiler support?
- The package metadata does not clearly establish Laravel compatibility, and its last release was February 2023. You should verify PHP and Composer constraints against your target Laravel, Symfony, and PSR versions in a sandbox. Because of the stale release cadence, assume future PHP or Laravel upgrades may require patching, forking, or replacement.
- What performance data does yiisoft/profiler capture?
- The package records timings and memory usage and supports custom checkpoints, which is useful for generic profile spans. The available context does not confirm built-in capture for SQL queries, HTTP requests, queue jobs, or Artisan command execution. Validate exactly what it captures before treating it as a replacement for Laravel Telescope or an APM tool.
- How would I integrate yiisoft/profiler with Laravel middleware, jobs, and Artisan commands?
- Plan a thin Laravel adapter with a service provider, configuration, environment-based enable/disable, and optional sampling. Instrument one low-risk endpoint, one queued job, and one Artisan command first, then compare the output and overhead against Telescope or Clockwork. Keep the integration isolated so it can be removed or replaced without affecting application code.
- Is yiisoft/profiler safe to run in production?
- Production adoption is high risk because profiling adds runtime overhead and can create memory or storage pressure if enabled broadly. Enable it only in development or on sampled, low-risk paths until overhead is measured. The stale release history and low community validation also raise the due-diligence burden for production use.
- What are the best alternatives to yiisoft/profiler for Laravel profiling?
- For most Laravel teams, Telescope, Clockwork, Laravel Debugbar, Xdebug, OpenTelemetry, or a commercial APM are stronger starting points. yiisoft/profiler is only worth considering if you specifically need a generic PHP profiler core and are willing to own the Laravel adapter. Do not replace Laravel-native observability without a measured reason.
- Is yiisoft/profiler actively maintained and what license does it use?
- The package uses the permissive BSD-3-Clause license, so legal risk is low. However, the last release was February 2023, repository metadata is weak, and community validation is limited, so maintenance and compatibility risk are the main concerns. Treat it as externally maintained but effectively internal for your stack, and budget time for patches or a fork.
Weaver
How can I help you explore Laravel packages today?