New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MISP Pull takes forever and other performance issues. #7201
Comments
Hello, Is it only for PULL or are you noticing the same slowness for other usage? Could you also provide more information about
Thanks |
OS Used : The hardware (memory, cpu, sdd/hdd, ...): The usage of the instance (#users, #correlations, #attributes & events, ...) How is the remote end performing (if the remote server is slow, it's normal that the PULL is taking time)? It's not just the pull, some other pages take too long to respond (administration -> jobs, audit -> logs ) |
Sorry, it's running on a VM , SSD |
Indeed, if the remote end is very slow, it will also slow down the pull process on your instance.
However, these pages should not be slow as they are paginated. Just out of curiosity, how many entry do you have for your job and audit logs?
The usage of the instance seems good. Around 50 attributes per events is a nice balance. However, please note that if you have lots of small events and some very large ones (containing +100000 attributes), it could explain the slowness of your instance. May I ask how much memory does your VM provide as well as the Thanks! |
memory_limit (2048 MB)… OK (recommended: 2048 MB) |
System is 99% idle but MISP is ultra slow.
v2.4.136 is the version running on a Ubuntu 20.04.
Any pointers on how to troubleshoot performance on MISP ?
The text was updated successfully, but these errors were encountered: