#Crashing when doing large operations or schematic imports

1 messages · Page 1 of 1 (latest)

sterile wingBOT
#

@acoustic pelican uploaded a log, Hi there!

I am setting up a Multiplayer server and doing some testing with Axiom. When I (or others) try to import a schematic, or do a larger operation our clients will lock up and provide a timed out error.

These files are larger for schematics. Abut 1.5mil blocks not accounting for air (which we usually don't paste in anyways). Singleplayer performance is as expected with quick pastes.

Client Logs:
Server Logs:

MC v1.20.1 + Axiom 3.0.0 for Fabric + Fabric Loader 0.15.11 + Fabric API 0.92.2+1.20.1

  • Fabric 0.15.11 on 1.20.1
#

@acoustic pelican uploaded a log, Hi there!

I am setting up a Multiplayer server and doing some testing with Axiom. When I (or others) try to import a schematic, or do a larger operation our clients will lock up and provide a timed out error.

These files are larger for schematics. Abut 1.5mil blocks not accounting for air (which we usually don't paste in anyways). Singleplayer performance is as expected with quick pastes.

Client Logs:
Server Logs:

MC v1.20.1 + Axiom 3.0.0 for Fabric + Fabric Loader 0.15.11 + Fabric API 0.92.2+1.20.1

  • Fabric 0.15.11 on 1.20.1
acoustic pelican
#

You can see where I dropped out and the paste also stopped in it's tracks. Doesn't crash other clients unless they're in the same chunk as the operation.

scarlet vortex
#

The logs you sent do not indicate any crash

acoustic pelican
#

They do show my issue though you can see at the points I highlighted the client being timed out for the operation

#

Sorry for using the wrong term

scarlet vortex
#

So the server isn't strong enough to process it before you get disconnected?

#

What do you want me to do about that

acoustic pelican
#

Is that why the client keeps timing out? Would you suggest adding a specific resource - I haven’t observed compute or memory being swallowed by axiom but I can try to watch closer.

scarlet vortex
#

Could just be the network is too slow to send 1.5m blocks

#

It'd have to be really slow for that to be the case though

#

Try doing a spark profile or something while it's pasting

acoustic pelican
#

I’ll give that a shot. Hadn’t really considered the network it’s normally solid as a rock.

#

Also while I have you — is there any config option for disabling lighting updates after an operation, like skip the relighting task?

scarlet vortex
#

No