Level 31
What makes you think it is high usage?
Do you have unnecessary PHP extensions enabled, like xdebug?
Are there any real performance problems or you're just frightened by 30 Mb consumption?
1 like
Oct 22, 2025
7
Level 1
High memory usage on every request
Hi,
I just installed clockwork so that I can observe and optimize heavy queries, and I noticed that every request, even the built-in api/health-check consumes 28~35mb memory.
At first, I thought it was an issue related to clockwork, so I decided to try telescope, and it also reports the same memory usage.
By the way, the project is running on docker container locally. I'm not particularly sure, but could it be the reason why?
EDIT:
Tried the following as stated in the documentation.
xdebug.mode = profile xdebug.start_with_request = trigger xdebug.profiler_output_name = cachegrind.out.%u.%r
also tried the following DataSources:
PhpDataSource
LaravelDataSource
but still doesn't change a thing
Level 1
I'm aware it's pretty normal and that it's not the actual consumption of the request itself... but it would be hard to benchmark with having that memory as the base/default.
also, i don't think it's xdebug's fault, since I had its mode set to coverage only.
Level 73
I recommend using the Laravel Debugbar, it's light weight
1 like
Level 1
Yeah, unfortunately, mine's a headless api.
Level 75
so that I can observe and optimize heavy queries
Give an example of what you call a heavy query.
And are you using pagination?
Level 1
i don't think this matters...
because as I've mentioned, even a health-check, or Route::get('test', fn () => 'Hello'); still reports 28~35mb memory usage
Level 75
Clockwork will use more memory. I would guess that your:
Route::get('test', fn () => 'Hello');
Is probably using only around 3mb of memory.
Try https://www.php.net/manual/en/function.memory-get-usage.php
But without clockwork.
Please or to participate in this conversation.