-
Notifications
You must be signed in to change notification settings - Fork 633
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
[Bug] Slow loading of TheHive because of Tags #1869
Comments
The issue here is that you have 7k+ tags. I'm pretty sure you have "data" in your tags, like emails, ids, etc.. but well this comes from how TheHive 3 is used.
I'm not sure this assumption is true, except if each case comes with 10 new/distinct tags (which is not the right way of doing things). Anyways, we will think of how to improve this but we need the tags data if we want to display the colours... |
@nadouani Thank you. |
OK I get it for the observables. I get if for TheHive 3 and custom fields. Now with 20k cases => 20k Alert Ids as tags. A I support, thousands of alerts and observables with their tags. This is in fact a use case we didn't though about. We have to brainstorm here to come up with a solution |
Found a solution: Have the free tags cache API only load the free tags that defined a custom colour instead of loading all the tags ;) |
@nadouani Thanks, sounds great and should work :) Does this affect Auto-complete? Another idear came in my mind this night, so I just wanted to share it with you: |
No, auto complete relies on an API |
Request Type
Bug
Work Environment
Problem Description
Starting the TheHive page or directly jumping to a case using a link takes several times.
/api/v1/query?name=list-tags The Tag-List on my test system with 800 Cases and 7366 Tags is about 2 MB. That means on my prod system the tag-list with arround 20000 Cases is more than 20x slowerBy analyzing this, the root-cause seems to be related to URL:
Unfortunately this prevents me from migrating to 4.1 in Prod :-(
Possible Solutions
Do not provide Tag-list to FE and auto-complete Tag list based on backend.
It seems that this functionality is only used for auto-complete.
Alternative specify which tags should be auto-completed (e.g. all non-free tags).
BTW: Why are there 2 ~chars in the URL of a case? /index.html#!/case/~~44187888/details
Solution
The solution is to cache only the free tags that define a custom colour:
/api/status
outputThe text was updated successfully, but these errors were encountered: