← Back to feedback
Feedback Open

Performance issues

ScienceofDishwashing · 21d ago

Hey, I love the toolbox in every way. The only thing is that if the factory gets pretty large, like defining 10 different items as output and let it auto-complete the factory, the site ceases to function. Is the tool just not made for large auto-resolves like this? Am I doing something wrong? Which Browser do you recommend? If its a server resources problem, could I get a local version I can run on my homeserver?

4 comments

  • ScienceofDishwashing · 21d ago

    Ok, I saw, that youre planning on releasing a Desktop app?

  • ScienceofDishwashing · 15d ago

    I saw that you adressed the performance problem in your patchnotes, first of all thank you for adressing it so fast. But I think I broke it again. I think its mainly that the planner somehow sets up too many nodes if I define some Items as output. I think It would be good, If I could put an Item as an output node and the planner resolves it from there. Simmilar to Satisfactory Tools.

  • ScienceofDishwashing · 15d ago

    I also constantly get the error, that something cant be produced with the current resource limits. The Limits are pretty low compared to Satisfactory Tools. Is the Planner only Counting non boosted limits? I sadly couldnt try what happens if I up the limits to the same as ST cause it froze on me again ^^.

  • Xuqari maintainer · 21h ago

    Thank you for coming back with the detail, it helps a lot. Three answers. The freeze. The part I fixed in v0.19.4 was the belt router, the code that draws the lines between machines so they never touch; it did a tenth of the work it used to and the auto-plans I could build here stopped locking the page. If yours still does, it is the next layer down: the solver itself, which runs once per machine the plan adds, so a plan with hundreds of machines pays for it hundreds of times. That is a bigger rewrite I am already in the middle of, and a real plan that trips it would be the best test case I could have. If you can, build the plan up to the point where it still responds, hit Share on the factory and paste the link here, and tell me the browser. The resource limits. The default limit for each raw is every node on the map mined with a Mk.3 miner at 100%. Satisfactory Tools lists the same nodes at 250%, so its numbers are two and a half times ours. You can raise any limit in the factory config (the ⚙ next to Balance): type the number you want and the "cannot be produced within the resource limits" message goes away. Making the default clearer, or letting you pick the clock the limits assume, is a fair ask and I have noted it. Too many nodes. Today Balance re-plans each product's tree on its own, which is why ten outputs grow into a large graph. Planning from an output node, the way Satisfactory Tools does, is exactly where the new solver is heading. Leaving this open until it is there.

Sign in to vote or comment.