-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Large Network performance issues #1460
Comments
Thanks for reporting! |
Thanks for looking into this. For the second log, do you think this is something I should raise up to the Sophisticated Storage team? |
I'll look into it myself first. But it may be needed later. |
Sounds good, just let me know if it gets to that point and you want be to reach out to them. Thanks. |
@rhullah I just looked into this a bit. Here are my findings: I'm not sure about the first log, especially since breaking/replacing it fixed the issue. For the second log, I think we're running into the limits here of ID accessing third-party storage systems via the regular item handler API. An Integrated Storage addon has been on my todo list for a long time now for reasons like these... |
Or lowering your exporter's tick rate would also help of course. |
I've finally added an issue on their GH. Hopefully something can come of it. |
Issue type:
Short description:
Was noticing some lag in my game, so I took some Spark profiles. Both mostly pointed towards IntDyn so I wanted to share them in hopes that there might be something to be done to improve performance. After the first one I ran some network diagnostics and found two aspects that were not working.
First Profile: https://spark.lucko.me/fO9jf7CetA
I then ran another profile.
Second Profile: https://spark.lucko.me/zlpvnleX1n
Which is better than the first, but still not the greatest. My network which was primarily used for everything (crafting and storage) is now mostly used for logistics, brining stuff in/out of the network. So besides it being a large/high item count network, it shouldn't be a doing a lot of active stuff.
Steps to reproduce the problem:
I'm not sure as I think it's associated to being a large/high item count network.
Versions:
Profiler output:
See above.
The text was updated successfully, but these errors were encountered: