Laravel Telescope In Production Affects Performance?
Hi
I've been using Laravel Telescope in local and staging server and is incredibly useful, but now that I have my production server, I found that I am already dependent on telescope. So I would like to use it on production but I'm concerned about the performance impact because it does a lot of things. However I think I only need to activate the exceptions module and maybe one or two more.
Do you recommend it? or do you tweak something to don't impact too much on performance?
Telescope provides list of watchers that you can enable or disable based on the environment. You can look at all here.
But also there is a nice play/pause button on telescope which you can use whenever you want to debug something that happened on the production server for example. The only modification that I do is I allow the telescope dashboard only for my personal email address, so that only I have access to it here is how, but I still use it on production, it is a really nice tool.
@Nakov@snapey We have a laravel project which is using a lot of queues, is there any alternative to Telescope so we can use it in production to manage queues (and possibly retry queues manually). Or maybe we can use Telescope in productions but turn off other features like log viewer... In general what is your advice to manage/monitor queues? Thank you
I would not suggest to use Telescope in production as enabling it in a production environment can have a performance impact, primarily in terms of increased memory usage, database overhead, network latency, and storage requirements.
Also the laravel documentation is also mainly focused on installation in local development only.
I have added telescope to my legacy project in laravel 6 and I can say that this package has big impact on app performance.
time response from ~600ms increased to ~2s
