Describe the bug
So when you do ray()->measure("ha"); ray()->measure("ha"); you get this
which pretty much loses all the sense to use since it measures the trip time to report the timer to ray (I guess?).
Additionally, would it be a possibility to somehow do the reporting asynchronously/not slow down the application execution due to the trip time of the payloads?
The solution to the first problem is avoidable by passing the closure, but only if you measure one thing at the time. Wouldn't it make more sense to do the requests to ray differently or at least measure the time of the request it is sent to ray & calculate the difference?
Versions
Ray version (you can see this in "About Ray"): any
PHP version: 8.0
Laravel version (if applicable): 8.XX
Describe the bug So when you do
ray()->measure("ha"); ray()->measure("ha");you get thiswhich pretty much loses all the sense to use since it measures the trip time to report the timer to ray (I guess?).
Additionally, would it be a possibility to somehow do the reporting asynchronously/not slow down the application execution due to the trip time of the payloads?
The solution to the first problem is avoidable by passing the closure, but only if you measure one thing at the time. Wouldn't it make more sense to do the requests to ray differently or at least measure the time of the request it is sent to ray & calculate the difference?
Versions Ray version (you can see this in "About Ray"): any
PHP version: 8.0 Laravel version (if applicable): 8.XX