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
After researching this, it seems the high CPU usage is only when using Eventlet. I did a bit of digging into Eventlet to try to figure out why, but I got lost pretty quick with what's doing what. Appears to be at the socket level with all the trampolining while calling send.
Easiest solution for a tool like the swiftly cli is to not bother with Eventlet by default, but I'll make it into an option so users can decide. The swiftly library itself certainly has many use cases where Eventlet would be preferred, and I'll keep it using Eventlet by default, but allow not using it even if it is installed.
The text was updated successfully, but these errors were encountered:
After researching this, it seems the high CPU usage is only when using Eventlet. I did a bit of digging into Eventlet to try to figure out why, but I got lost pretty quick with what's doing what. Appears to be at the socket level with all the trampolining while calling send.
Easiest solution for a tool like the swiftly cli is to not bother with Eventlet by default, but I'll make it into an option so users can decide. The swiftly library itself certainly has many use cases where Eventlet would be preferred, and I'll keep it using Eventlet by default, but allow not using it even if it is installed.
The text was updated successfully, but these errors were encountered: