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
When queuing a ot lof server scans, SSLyze's memory usage increases significantly. For example, queuing 100 server scans results the SSLyze process taking 1.5 GB of memory, which seems huge. This makes it difficult to deploy SSLyze in environments with limited RAM (such as AWS Lambda).
After investigating, this is due to the fact that SSLyze relies on Python's ThreadPoolExecutor, which uses a lot of memory when submitting a large number of jobs:
When queuing a ot lof server scans, SSLyze's memory usage increases significantly. For example, queuing 100 server scans results the SSLyze process taking 1.5 GB of memory, which seems huge. This makes it difficult to deploy SSLyze in environments with limited RAM (such as AWS Lambda).
After investigating, this is due to the fact that SSLyze relies on Python's ThreadPoolExecutor, which uses a lot of memory when submitting a large number of jobs:
The text was updated successfully, but these errors were encountered: