You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently upgraded from the legacy raven module (v1.2.0) to @sentry/node (v4.6.4). As soon as I did this my server had crazy memory leaks and CPU spikes. I have narrowed it down to this update as its the only thing that was changed and as soon as I reverted back to the legacy modules it stopped happening.
Here you can see the CPU spikes, then I start my process and then the CPU spikes again.
Here are the 3 process I am running with 1 using up 1.4GB.
I am not sure where to go from here. There are no errors being thrown and when the CPU is spikng the requests are slow but still completing. There is very little indication as to what is happening except that the update is what caused it. If there is more information I can provide to please let me know. For now I have reverted and will stay like that until I can determine what is happening.
The text was updated successfully, but these errors were encountered:
Package + Version
@sentry/node
Version:
Description
I recently upgraded from the legacy raven module (v1.2.0) to @sentry/node (v4.6.4). As soon as I did this my server had crazy memory leaks and CPU spikes. I have narrowed it down to this update as its the only thing that was changed and as soon as I reverted back to the legacy modules it stopped happening.
Here you can see the CPU spikes, then I start my process and then the CPU spikes again.
Here are the 3 process I am running with 1 using up 1.4GB.
I am not sure where to go from here. There are no errors being thrown and when the CPU is spikng the requests are slow but still completing. There is very little indication as to what is happening except that the update is what caused it. If there is more information I can provide to please let me know. For now I have reverted and will stay like that until I can determine what is happening.
The text was updated successfully, but these errors were encountered: