-
-
Notifications
You must be signed in to change notification settings - Fork 868
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
How to improve the issue of management page lag when the system tag exceeds 5000? #872
Comments
Node.js cannot be multi-threaded. Let me test it, 5000 points, for opcua, set it to refresh in 30 seconds. If the refresh time is too small, it won't be able to handle it. |
This is determined by the mechanism of Node.js itself. My current solution is that I build multiple sites, split the points, each site does not exceed 2000 points. My projects generally have around 30 million points, or even more. |
The running stability is not bad, I have a project, I have used fuxa for more than 2 years, and it is still running stably. |
Hello, are multiple fuxa deployed on the same computer? |
It's all right, I usually deploy multiple sites on one computer and deploy multiple computers. |
Hi, I have tested using the new version and now the report is as follows:
|
Do you have any tutorials in this area? |
Hi, sorry for the delay, do you mean that without going into edit mode and having disabled broadcasting of all tags, the views work correctly? and the problem is still if you go to edit the device? |
I assume the issue has been resolved in the meanwhile. I'm therefore going to close this issue. |
Hi, I have an idea to use FUXA on projects with more than 5000 system tag . Currently, during simulation testing, there was a serious lag in the management page at 5000 system tag . How can I improve this problem?
Cmd error
(node:11564) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 finish listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
The text was updated successfully, but these errors were encountered: