You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm finding that //move is horribly slow. For example, consider the following structure measuring about 56x50x200 (so ~560'000 nodes, of which around 100'000 are not air):
Moving this thing by 25 meters in the -X direction took 18 minutes with Minetest built in Debug mode (I did not try it in Release mode). The majority of that time was spent with the engine really not using much CPU (20% to 70% of one core, largely variable), until the very end, where it spiked to 100% for about one minute before the server finally "woke up" and showed me the result of the move.
The move was successful, despite the long wait.
It's slow enough that, suppose I //load a schematic... beyond some size (not sure how big), it's faster to erase the building with //set air, do //1 at a new target, and //load the schematic again, than it is to just //load it once and //move it where it needs to go.
The text was updated successfully, but these errors were encountered:
I'm finding that
//move
is horribly slow. For example, consider the following structure measuring about 56x50x200 (so ~560'000 nodes, of which around 100'000 are not air):Moving this thing by 25 meters in the -X direction took 18 minutes with Minetest built in Debug mode (I did not try it in Release mode). The majority of that time was spent with the engine really not using much CPU (20% to 70% of one core, largely variable), until the very end, where it spiked to 100% for about one minute before the server finally "woke up" and showed me the result of the move.
The move was successful, despite the long wait.
It's slow enough that, suppose I
//load
a schematic... beyond some size (not sure how big), it's faster to erase the building with//set air
, do//1
at a new target, and//load
the schematic again, than it is to just//load
it once and//move
it where it needs to go.The text was updated successfully, but these errors were encountered: