Download the PHP package ctohm/laravel-request-profiler without Composer
On this page you can find all versions of the php package ctohm/laravel-request-profiler. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download ctohm/laravel-request-profiler
More information about ctohm/laravel-request-profiler
Files in ctohm/laravel-request-profiler
Package laravel-request-profiler
Short Description Prints request profiling to a file under storage/logs
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-request-profiler
Laravel Request Profiler
Laravel Request Profiles is a package that will enable putting marks in your code to identify your application bottlenecks.
Once installed, publish the config file by doing
The service provider will autoregister a singleton app('timings') that you can use to push timing marks into a
dedicated message bag. We suggest starting up the timings messagebag as early as possible in the request lifecycle. For
example, in the TrustProxies middleware. In the same middleware you can call the method to wrap up the timings
for the current request when returning the output of $next($request).
Every time you use the app('timings')->pushTiming() statement, a new mark will be recorded by the profiler, as if it was a breakpoint. In the image above, you can see the final output:
- The upper section shows the spl object id of the request and its uuid, as well as the requested path.
- The lower section shows the file, the line where
pushTimingwas called, the incremental timing from the last call and the total time up to that point. - Finally, the total ovewall time is shown.
Inspect the collected timings by doing
All versions of laravel-request-profiler with dependencies
kint-php/kint Version ^3.3
illuminate/support Version ^8.32 || ^9.0 || ^10 || ^11