mod LAG impact comparison [closed]

User avatar
runs
Member
Posts: 3225
Joined: Sat Oct 27, 2018 08:32

Re: mod LAG impact comparison

by runs » Post

THE SAMZ VS JUANCHI

Samz
samz.png
samz.png (129.65 KiB) Viewed 2562 times
Juanchi
juanchi.png
juanchi.png (129.29 KiB) Viewed 2562 times
Initial conditions:
-Empty new world
-Test time: Less than a minute.
-Benchmark: htop

Minetest open 11 threads in the CPU.

Analysis:
- Samz consumes less memory: 2% vs 12%
- Juanchi consumes less CPU, but in a empty world, obviously in more heavy game. But it is necesaary to increase the test time and check in intensive situations.

User avatar
runs
Member
Posts: 3225
Joined: Sat Oct 27, 2018 08:32

Re: mod LAG impact comparison

by runs » Post

investigation.png
investigation.png (101.15 KiB) Viewed 2553 times
The 7 first threads are referred to the engine. The 4 remaining are for the game.

User avatar
Festus1965
Member
Posts: 4181
Joined: Sun Jan 03, 2016 11:58
GitHub: Festus1965
In-game: Festus1965 Thomas Thailand Explorer
Location: Thailand ChiangMai
Contact:

mod LAG impact comparison - game juanchi

by Festus1965 » Post

juanchi : game
runs wrote:
Sat May 14, 2022 13:49
THE SAMZ VS JUANCHI

Initial conditions:
-Empty new world
-Test time: Less than a minute.
-Benchmark: htop

Minetest open 11 threads in the CPU.

Analysis:
- Samz consumes less memory: 2% vs 12%
- Juanchi consumes less CPU, but in a empty world, obviously in more heavy game. But it is necessary to increase the test time and check in intensive situations.
interesting, but you compare there
* a game (samz)
with
* a game (juanchi)
but without any measurements, that could be used to compare to yet data (profiler) of existing game looked into (mtg, mineclone)

My intention might be:
* compare now game to game : start just let run game juanchi as usual, 10-11 hours
then
* use game samz, with same conditions
so that I have also data to compare this both with mtg and Mineclone

... but also have to let run mtg and mineclone also again, with gathering also CPU, Memory data to compare back.


But even mtg is a base, samz and juanchi seam to be more fully ready house on a base included.
That is more like compare to my running server maybe ?


source:
https://github.com/runsy/juanchi
c07895b / Mar 19.03.2022


on 5.6.0-dev engine


just I download the game, set it and start:

Code: Select all

minetestserver --world .minetest/worlds/engine550 --config .minetest/engine550.conf --port 30005 --gameid juanchi
2022-05-15 06:08:16: [Main]: Using game specified by --gameid on the command line
2022-05-15 06:08:16: WARNING[Main]: Mod on_eat at /usr/local/share/minetest/games/juanchi/mods/on_eat:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: Undeclared global variable "vote" accessed at /usr/local/share/minetest/games/juanchi/mods/mpd/init.lua:217
2022-05-15 06:08:16: WARNING[Main]: Mod schemedit at /usr/local/share/minetest/games/juanchi/mods/minetest_schemedit:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod killme at /usr/local/share/minetest/games/juanchi/mods/killme:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: Mod intllib at /usr/local/share/minetest/games/juanchi/mods/intllib:
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: ACTION[Main]: hb.register_hudbar: health
2022-05-15 06:08:16: ACTION[Main]: hb.register_hudbar: breath
2022-05-15 06:08:16: ACTION[Main]: [mana] mana.mt opened.
2022-05-15 06:08:16: [Main]: [mana] mana.mt successfully read.
2022-05-15 06:08:16: ACTION[Main]: hb.register_hudbar: mana
2022-05-15 06:08:16: WARNING[Main]: Mod hbarmor at /usr/local/share/minetest/games/juanchi/mods/hbarmor:
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: intllib.Getter is deprecated. Please use intllib.make_gettext_pair instead. (called from ...local/share/minetest/games/juanchi/mods/hbarmor/init.lua:3) (at ...local/share/minetest/games/juanchi/mods/hbarmor/init.lua:3)
2022-05-15 06:08:16: ACTION[Main]: hb.register_hudbar: armor
2022-05-15 06:08:16: WARNING[Main]: Mod explosions at /usr/local/share/minetest/games/juanchi/mods/explosions:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: Mod dlg at /usr/local/share/minetest/games/juanchi/mods/dlg:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: Mod cute_deco at /usr/local/share/minetest/games/juanchi/mods/cute_deco:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: Mod bedrock2 at /usr/local/share/minetest/games/juanchi/mods/bedrock2:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod tree_stairs at /usr/local/share/minetest/games/juanchi/mods/tree_stairs:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod trash_can at /usr/local/share/minetest/games/juanchi/mods/trash_can:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Mod nyancat at /usr/local/share/minetest/games/juanchi/mods/nyancat:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod flower_pot at /usr/local/share/minetest/games/juanchi/mods/flower_pot:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod fishing at /usr/local/share/minetest/games/juanchi/mods/fishing:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Mod anvil at /usr/local/share/minetest/games/juanchi/mods/anvil:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: WARNING: minetest.setting_* functions are deprecated.  Use methods on the minetest.settings object. (at /usr/local/share/minetest/games/juanchi/mods/anvil/init.lua:16)
2022-05-15 06:08:16: WARNING[Main]: Mod quartz at /usr/local/share/minetest/games/juanchi/mods/quartz:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Field "noise_threshhold": Deprecated: new name is "noise_threshold".
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Mod ambience at /usr/local/share/minetest/games/juanchi/mods/ambience:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
[MOD] Ambience Lite loaded
2022-05-15 06:08:16: WARNING[Main]: Mod lucky_block at /usr/local/share/minetest/games/juanchi/mods/lucky_block:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Mod fireworkz at /usr/local/share/minetest/games/juanchi/mods/fireworkz:
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Field "height_min": Deprecated: new name is "y_min".
2022-05-15 06:08:16: WARNING[Main]: Field "height_max": Deprecated: new name is "y_max".
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Mod bike at /usr/local/share/minetest/games/juanchi/mods/bike:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod beacons at /usr/local/share/minetest/games/juanchi/mods/beacons:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Mod abriglass at /usr/local/share/minetest/games/juanchi/mods/abriglass:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Mod hangglider at /usr/local/share/minetest/games/juanchi/mods/hangglider:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod carpets at /usr/local/share/minetest/games/juanchi/mods/carpets:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod ropes at /usr/local/share/minetest/games/juanchi/mods/ropes:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
[Ropes] Loaded!
2022-05-15 06:08:16: WARNING[Main]: Mod cannons at /usr/local/share/minetest/games/juanchi/mods/cannons:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: ACTION[Main]: [boost_cart] Overwriting definitions of similar carts mod
2022-05-15 06:08:16: WARNING[Main]: Undeclared global variable "chains_sbox" accessed at ...e/minetest/games/juanchi/mods/basic_materials/metals.lua:131
2022-05-15 06:08:16: WARNING[Main]: Undeclared global variable "chains_sbox" accessed at ...e/minetest/games/juanchi/mods/basic_materials/metals.lua:145
2022-05-15 06:08:16: WARNING[Main]: No craft recipe known for output
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
[3d_armor] Fire Nodes disabled
2022-05-15 06:08:16: WARNING[Main]: Mod rainbow_ore at /usr/local/share/minetest/games/juanchi/mods/rainbow_ore:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Field "tile_images": Deprecated; new name is "tiles".
2022-05-15 06:08:16: WARNING[Main]: Field "height_min": Deprecated: new name is "y_min".
2022-05-15 06:08:16: WARNING[Main]: Field "height_max": Deprecated: new name is "y_max".
2022-05-15 06:08:16: WARNING[Main]: 3d_armor_ui: Mod loaded but unused.
2022-05-15 06:08:16: WARNING[Main]: @3d_armor_ip)3d_armor_ip: Mod loaded but unused.

2022-05-15 06:08:16: WARNING[Main]: Mod lantern at /usr/local/share/minetest/games/juanchi/mods/lantern:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod emeralds at /usr/local/share/minetest/games/juanchi/mods/emeralds:
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod crops at /usr/local/share/minetest/games/juanchi/mods/crops:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: ACTION[Main]: [crops] Loaded!
2022-05-15 06:08:16: WARNING[Main]: Mod bonemeal at /usr/local/share/minetest/games/juanchi/mods/bonemeal:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
@bonemeal)[MOD] bonemeal loaded

2022-05-15 06:08:16: WARNING[Main]: Not registering alias, item with same name is already defined: petz:horseshoe -> mobs:horseshoe_steel
2022-05-15 06:08:16: WARNING[Main]: Not registering alias, item with same name is already defined: petz:cheese -> mobs:cheese
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-15 06:08:16: WARNING[Main]: Overwriting stairs node: stairs:stair_adobe_brick
2022-05-15 06:08:16: WARNING[Main]: Overwriting stairs node: stairs:stair_inner_adobe_brick
2022-05-15 06:08:16: WARNING[Main]: Overwriting stairs node: stairs:stair_outer_adobe_brick
2022-05-15 06:08:16: WARNING[Main]: Overwriting stairs node: stairs:slab_adobe_brick
2022-05-15 06:08:16: WARNING[Main]: Mod pathfinder at /usr/local/share/minetest/games/juanchi/mods/pathfinder:
2022-05-15 06:08:16: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-15 06:08:16: WARNING[Main]: Mod campfire at /usr/local/share/minetest/games/juanchi/mods/campfire:
2022-05-15 06:08:16: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
         __.               __.                 __.  
  _____ |__| ____   _____ /  |_  _____  _____ /  |_ 
 /     \|  |/    \ /  __ \    _\/  __ \/   __>    _\
|  Y Y  \  |   |  \   ___/|  | |   ___/\___  \|  |  
|__|_|  /  |___|  /\______>  |  \______>_____/|  |  
      \/ \/     \/         \/                  \/   
2022-05-15 06:08:17: ACTION[Main]: World at [.minetest/worlds/engine550]
2022-05-15 06:08:17: ACTION[Main]: Server for gameid="juanchi" listening on 0.0.0.0:30005.
[MOD] Lucky Blocks loaded (175 in total)
running ... login short worked ... so here we go and wait ...

4 core / 8 threads : 32 GB Ram
so far 0.0 - 0.7 % CPU, 0.2 % Memory (or compare to 16 GB = 0.4 %)

/fast sneak in /profiler: (more like starting peaking ones)
* eraz : 23.5 %
* petz : 11.5 % (can compare to only petz in MTG)
* hudbars : 11.4 %
* hbarmor : 10.0 %
* itemhandling : 8.2 %
* mpd : 5.7 %
* climatez : 4.7 %
* mana : 4/4 %
* player_api : 3.8 % (to use as some reference)
* 3d_armor : 3.4 %
* hudinfo : 3.4 %
* ambience : 2.7 %
* schemedit : 2.4 %
* sailing_kit : 2.3 %
* fire : 1.6 (also known)

fast possible compare out of this:
* as a game : to MTG with also as 0.7-2.0 % CPU, used MEM 3.9%
less impact (empty world, no gamer !)

* as a game : to MTG with * player_api : 75.2 %, * fire : 24.8 %
a lot more other 'impact' mods as player_api just a part of 3.8 % here now (just started) ... will change after 11 hours
(but on my server with pipeworks+technic player_api also just have left a part of 4.0 %, fire 0.6% - so load might be similar already)

* as one mod : mod petz against mod petz included in game juanchi
as petz only in mtg : petz : 69.1 %, player_api: : 22.6 %, fire : 8.3 % has even no change to chow up yet as of a lot more concurrence loaded mods - but also here - let us wait for 10-11 hours run.


result after near 10 hours: no comment yet, have no time

Code: Select all

(T@__builtin)A total of F497704E sample(s) were taken.E


 instrumentation                                         |    min µs |    max µs |    avg µs | min % | max % | avg %
-------------------------------------------------------- | --------- | --------- | --------- | ----- | ----- | ------

 eraz:                                                   |         1 |       154 |         5 |   0.1 |  89.0 |  23.5
  - globalstep[1] .....................................  |         1 |       154 |         5 |   0.1 |  89.0 |  23.5
  - on_leaveplayer[1] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2

 hudbars:                                                |         0 |       124 |         2 |   0.0 |  84.7 |  12.3
  - globalstep[1] .....................................  |         1 |       124 |         3 |   0.0 |  84.7 |  13.6
  - on_leaveplayer[1] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2
  - on_joinplayer[1] ..................................  |        61 |        77 |        69 |   0.9 |  10.8 |   5.8

 hbarmor:                                                |         0 |       162 |         2 |   0.0 |  87.6 |  11.5
  - globalstep[1] .....................................  |         1 |       162 |         2 |   0.0 |  87.6 |  11.7
  - on_leaveplayer[1] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2
  - on_joinplayer[1] ..................................  |         2 |         3 |         2 |   0.0 |   0.4 |   0.2

 petz:                                                   |         0 |       143 |         2 |   0.0 |  85.4 |   9.7
  - globalstep[1] .....................................  |         1 |       143 |         1 |   0.0 |  84.7 |   7.7
  - on_leaveplayer[4] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2
  - on_leaveplayer[3] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2
  - on_joinplayer[1] ..................................  |         2 |         3 |         2 |   0.0 |   0.4 |   0.2
  - on_leaveplayer[5] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2
  - globalstep[2] .....................................  |         1 |        85 |         1 |   0.2 |  72.4 |   4.2

 itemhandling:                                           |         0 |       130 |         2 |   0.0 |  86.9 |   8.4
  - globalstep[1] .....................................  |         1 |       130 |         2 |   0.0 |  86.9 |   8.7

 climatez:                                               |         0 |       131 |         1 |   0.0 |  87.9 |   4.8
  - globalstep[1] .....................................  |         1 |       131 |         1 |   0.0 |  87.9 |   5.2

 mpd:                                                    |         0 |       113 |         1 |   0.0 |  81.5 |   5.0
  - globalstep[1] .....................................  |         1 |       113 |         1 |   0.0 |  81.5 |   5.4

 mana:                                                   |         0 |       171 |         1 |   0.0 |  82.8 |   4.7
  - globalstep[1] .....................................  |         1 |        93 |         1 |   0.0 |  82.8 |   5.6
  - on_leaveplayer[1] .................................  |       169 |       169 |       169 |  36.6 |  36.6 |  36.6
  - on_joinplayer[1] ..................................  |        20 |        25 |        22 |   0.3 |   3.5 |   1.9

 3d_armor:                                               |         0 |       129 |         0 |   0.0 |  82.7 |   4.1
  - globalstep[1] .....................................  |         1 |       129 |         1 |   0.0 |  82.7 |   4.7
  - on_leaveplayer[1] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2
  - on_joinplayer[1] ..................................  |         3 |         4 |         3 |   0.0 |   0.5 |   0.3

 hudinfo:                                                |         0 |       124 |         0 |   0.0 |  85.1 |   4.0
  - globalstep[1] .....................................  |         1 |       124 |         1 |   0.0 |  85.1 |   4.7
  - on_leaveplayer[1] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2
  - on_joinplayer[1] ..................................  |        17 |        25 |        21 |   0.3 |   3.0 |   1.7

 schemedit:                                              |         0 |       252 |         0 |   0.0 |  83.8 |   2.6
  - globalstep[1] .....................................  |         1 |       252 |         1 |   0.0 |  83.8 |   4.6
  - on_leaveplayer[1] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2
  - on_joinplayer[1] ..................................  |         1 |         1 |         1 |   0.0 |   0.2 |   0.1

 player_api:                                             |         0 |       137 |         0 |   0.0 |  86.0 |   2.6
  - globalstep[1] .....................................  |         1 |       137 |         1 |   0.5 |  86.0 |   4.6
  - on_leaveplayer[1] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2
  - on_joinplayer[1] ..................................  |        55 |        77 |        66 |   0.9 |   9.7 |   5.3

 sailing_kit:                                            |         0 |       124 |         0 |   0.0 |  84.4 |   2.5
  - globalstep[1] .....................................  |         1 |       124 |         1 |   0.2 |  84.4 |   4.2

 ambience:                                               |         0 |       340 |         0 |   0.0 |  80.9 |   2.5
  - globalstep[1] .....................................  |         1 |       340 |         1 |   0.2 |  80.9 |   4.5

 fire:                                                   |         0 |       170 |         0 |   0.0 |  79.2 |   2.0
  - globalstep[1] .....................................  |         1 |       170 |         1 |   0.0 |  79.2 |   4.1
  - on_leaveplayer[1] .................................  |         1 |         1 |         1 |   0.2 |   0.2 |   0.2
but just
player_api: | 0 | 137 | 0 | 0.0 | 86.0 | 2.6
left with just 2.6 % = others are strong time taker :
just from my server with using it: no pipeworks/technic, other with ...
player_api: | 0 | 29153 | 133 | 0.0 | 99.5 | 18.7
player_api: | 0 | 37241 | 89 | 0.0 | 97.4 | 4.0
and remember how much it took anyway alone ...

that takes some research to compare.


continue 16.05.2022:
let us take 91.5% as MTG base from empty server check.
Most significant mod inside player_api is strong showing up with 86.8%, followed by fire with just 4.7%.
As main in silent, no gamer mod, player_api will NOT change its behavior and just do it's (useless) work, it is a stable position for a relationship.

So player_api in juanchi got with its normal steady work just 2.6 % inside juanchi game together.
This 2.6 % are from the real work equal to the 86.8 % on mtg alone.
The Multiplikator is so (86.8 / 2.6) = 33.385. Mean juanchi is 33 times the load of MTG itself.

mhh, proof other way ?
we have tested mod petz, that is included there.
Petz alone on mtg did 69.1 % with player_api had 22.6 % what is a Multiplikator of 3.05
Here in game juanchi it has just ! 9.7 % part against player_api with 2.6 %, what gives us a Multiplikator 3.73. That is near but too much different, more like guessing, but a good hint.

How I get a measurement to compare with MTGame itself ?
Bur for what? juanchi is a fully ready game based on MTG ... no need to compare them ?

Oh yes, should, or let the new admin get the empty CPU load,
and take an idea about rising for each gamer = reach 100% at some point and final.
admins decision then, less gamer but his believed game, or reduce it or another and get more gamer ?

There is no way to guess that, as on empty world nothing to load also.

Sure, that game is heavy, it has a huge impact ... but the Faktor is so high against to MTG base, that I can't believe it.
About 30 times of MTG itself. Normal, when there are several mods included, and even hard impact petz is not the leading one also, just Nr 4.
If they all would be stable, all time same usage, easy ... can calculate it back. But that is not right.

I try a bit sheet,
where MTG is one stack with the known %, and then I add another stack, ... could work ...
see you later ...
Last edited by Festus1965 on Mon May 16, 2022 04:30, edited 1 time in total.
Human has no future (climate change)
If urgend, you find me in Roblox (as CNXThomas)

User avatar
Festus1965
Member
Posts: 4181
Joined: Sun Jan 03, 2016 11:58
GitHub: Festus1965
In-game: Festus1965 Thomas Thailand Explorer
Location: Thailand ChiangMai
Contact:

mod LAG impact comparison - games samz

by Festus1965 » Post

samz

source : https://github.com/runsy/samz
329c32f / 12.05.2022

Code: Select all

2022-05-16 08:20:21: WARNING[Main]: Mod wield3d at /usr/local/share/minetest/games/samz/mods/wield3d:
2022-05-16 08:20:21: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
2022-05-16 08:20:21: WARNING[Main]: WARNING: minetest.setting_* functions are deprecated.  Use methods on the minetest.settings object. (at /usr/local/share/minetest/games/samz/mods/wield3d/init.lua:6)
2022-05-16 08:20:21: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-16 08:20:21: WARNING[Main]: Field "use_texture_alpha": Boolean values are deprecated; use the new choices
2022-05-16 08:20:21: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-16 08:20:21: WARNING[Main]: Field "alpha": Obsolete, only limited compatibility provided; replaced by "use_texture_alpha"
2022-05-16 08:20:21: WARNING[Main]: Mod foodz at /usr/local/share/minetest/games/samz/mods/foodz:
2022-05-16 08:20:21: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-16 08:20:21: WARNING[Main]: Mod eatz at /usr/local/share/minetest/games/samz/mods/eatz:
2022-05-16 08:20:21: WARNING[Main]: 	Mods not having a mod.conf file with the name is deprecated.
2022-05-16 08:20:21: WARNING[Main]: Mod bedrock2 at /usr/local/share/minetest/games/samz/mods/bedrock2:
2022-05-16 08:20:21: WARNING[Main]: 	depends.txt is deprecated, please use mod.conf instead.
2022-05-16 08:20:21: WARNING[Main]: 	description.txt is deprecated, please use mod.conf instead.
running ... crash hen login in for profiler = no results

Code: Select all

2022-05-16 19:32:54: 
ACTION[Server]: Thomas [192.168.x.x] joins game. List of players: Thomas
ACTION[Main]: Server: Shutting down
ACTION[Server]: Thomas leaves game. List of players: 
ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod 'playerz' in callback on_joinplayer(): .../local/share/minetest/games/samz/mods/playerz/cloths.lua:166: attempt to index local 'cloth_itemstack' (a nil value)
stack traceback:
.../local/share/minetest/games/samz/mods/playerz/cloths.lua:166: in function 'compose_cloth'
/usr/local/share/minetest/games/samz/mods/playerz/init.lua:53: in function 'func'
...ocal/share/minetest/builtin/profiler/instrumentation.lua:107: in function <...ocal/share/minetest/builtin/profiler/instrumentation.lua:100>
/usr/local/share/minetest/builtin/game/register.lua:429: in function </usr/local/share/minetest/builtin/game/register.lua:415>
Last edited by Festus1965 on Mon May 16, 2022 12:35, edited 1 time in total.
Human has no future (climate change)
If urgend, you find me in Roblox (as CNXThomas)

User avatar
Festus1965
Member
Posts: 4181
Joined: Sun Jan 03, 2016 11:58
GitHub: Festus1965
In-game: Festus1965 Thomas Thailand Explorer
Location: Thailand ChiangMai
Contact:

mod LAG impact comparison - proofed data

by Festus1965 » Post

here a summary of different options to measure,
and how this data works together

It is proofed that
* profiler save date
* CPU load
* Watt usage, and
* max_lag
ARE telling more ore less the truth.


profiler extract and CPU load are near proportional together:
Example: server AsiaThailand

profiler with mods pipeworls and technic + technic_aluminum are showing a bit more than 50% taken by pipeworks and technic,
and so also the htop of server
* Video : with pipeworks+technic are near double high then
* Video : without piepworks+technic

also a compare with step by step login (brave kids, that take me some icecream next meeting) show the different climb of CPU usage on both versions:
Image


I also made a proof of climbing Watt usage just between:
* running Ubuntu
* then with mt server empty
* and mt server with minetest-game, where player_api knocks in so hard = ~90% part of mtg usage
Video


The only thing about Watt and max_lag is that the effect onto both is not the same strong or %, but it is there.
Measured, and proofed to be connected proportional to the difference of profiler or CPU load, but in very small numbers - would need more accurate meter to detect exact.


So stop arguing against profiler ... as it is the easiest way as independent.

htop cpu load is different on every server as of CPU and frequency,
but the profiler load can easy be used as base.
profiler is builtin and clear enough for this measure.


For my server AsiaThailand yesterday it got clear,
that the loos by false mods pipeworks and technic (shown over 50% in profiler)
ALSO made a near exact 50% lost on CPU load at same gamer amount. (see pic above)

This mean, reducing the usage of high impact mods,
is also reducing lag
(remember max_lag is estimated !) or allow more gamer (loos 50% load = double gamer with same lag) in.
Your choice what to use for.

But this measurements (just via profiler) MAKE SENSE !
Human has no future (climate change)
If urgend, you find me in Roblox (as CNXThomas)

Maverick2797
Member
Posts: 128
Joined: Sun Aug 05, 2018 12:37
In-game: Maverick2797
Location: Poking about here and there...

Re: mod LAG impact comparison

by Maverick2797 » Post

Festus1965 wrote:
Fri May 13, 2022 23:36

advtrains all
* with screen : 29.9 Watt
* screensaver : 11.75 Watt
= add mod advtrains add 0.25 Watt work (to base MTG: empty world, no nodes, items of it)


summary, short:
* just MTG (with player_api) HAS a measurable plus in Watt then 'empty' game (Wuzzy)
* mod advtrains add another 0.25 Watt alone to MTG
= result of adding load seen at profiler, about 125 % energy usage more
What surprises me is that you're surprised that advtrains causes a computer to use more power...

Advtrains is a relatively complex mod from a fresh install, and once trains start running there's a lot going on in the background to ensure they keep running where they're supposed to, further increasing the complexity. Not to mention any LuaATC code used to run various functions on the rail network.

It's well established that a large advtrains network causes lag, but any mod run on that scale will.
The number you have called is not available during a solar eclipse. This message will self destruct in ten seconds in protest... [BEEP]

User avatar
Festus1965
Member
Posts: 4181
Joined: Sun Jan 03, 2016 11:58
GitHub: Festus1965
In-game: Festus1965 Thomas Thailand Explorer
Location: Thailand ChiangMai
Contact:

mod LAG impact comparison

by Festus1965 » Post

Maverick2797 wrote:
Tue May 17, 2022 12:52
What surprises me is that you're surprised that advtrains causes a computer to use more power...

Advtrains is a relatively complex mod from a fresh install, and once trains start running there's a lot going on in the background to ensure they keep running where they're supposed to, further increasing the complexity. Not to mention any LuaATC code used to run various functions on the rail network.

It's well established that a large advtrains network causes lag, but any mod run on that scale will.
IF there is a world with a lot of trains, I agree
but the measurement was done on an empty word without any !!! node or item from advtrains.

So, haha, sure that is surprising - other mods proofed that it goes also other way.

I mean:
No lag creating when not needed/used AND even near no lag even when used.

It is ok, when some modder don't mind about the admin - but it is also ok, when I tell it, so they know it before falling into the lag trap.
Human has no future (climate change)
If urgend, you find me in Roblox (as CNXThomas)

User avatar
jwmhjwmh
Developer
Posts: 125
Joined: Sun Jul 18, 2021 14:10
GitHub: TurkeyMcMac

Re: mod LAG impact comparison - proofed data

by jwmhjwmh » Post

Festus1965 wrote:
Mon May 16, 2022 02:10
I also made a proof of climbing Watt usage just between:
* running Ubuntu
* then with mt server empty
* and mt server with minetest-game, where player_api knocks in so hard = ~90% part of mtg usage
Did the empty server have Minetest Game active excluding player_api? I find it hard to believe player_api on its own has a significant impact when its average time per globalstep is 7 microseconds. I'm pretty sure the vast majority of the time was spent executing C++, which is not captured by the profiler.

User avatar
LMD
Member
Posts: 1386
Joined: Sat Apr 08, 2017 08:16
GitHub: appgurueu
IRC: appguru[eu]
In-game: LMD
Location: Germany
Contact:

Re: mod LAG impact comparison - proofed data

by LMD » Post

jwmhjwmh wrote:
Tue May 17, 2022 13:36
Did the empty server have Minetest Game active excluding player_api? I find it hard to believe player_api on its own has a significant impact when its average time per globalstep is 7 microseconds. I'm pretty sure the vast majority of the time was spent executing C++, which is not captured by the profiler.
I've tried to explain this to him many times (see the thread history). He doesn't seem to listen.
My stuff: Projects - Mods - Website

User avatar
Festus1965
Member
Posts: 4181
Joined: Sun Jan 03, 2016 11:58
GitHub: Festus1965
In-game: Festus1965 Thomas Thailand Explorer
Location: Thailand ChiangMai
Contact:

Re: mod LAG impact comparison - proofed data

by Festus1965 » Post

jwmhjwmh wrote:
Tue May 17, 2022 13:36
Did the empty server have Minetest Game active excluding player_api? I find it hard to believe player_api on its own has a significant impact when its average time per globalstep is 7 microseconds. I'm pretty sure the vast majority of the time was spent executing C++, which is not captured by the profiler.
here is that post about this test:

Yes, empty server was the 'game' empty by ??? that only included the mod ???, that left ONLY one detected mod '??' in profiler report.
Then only MTG with empty world and no gamer logged in

And yes I am listening, but whatever the player_api might ONLY use 7 microsecons or less or more,
IT HAS that impact ! ... in profiler very similar in htop AND also lag but less in Watt!
Last edited by Festus1965 on Thu May 19, 2022 01:51, edited 1 time in total.
Human has no future (climate change)
If urgend, you find me in Roblox (as CNXThomas)

User avatar
LMD
Member
Posts: 1386
Joined: Sat Apr 08, 2017 08:16
GitHub: appgurueu
IRC: appguru[eu]
In-game: LMD
Location: Germany
Contact:

Re: mod LAG impact comparison - proofed data

by LMD » Post

Festus1965 wrote:
Wed May 18, 2022 00:01
IT HAS that impact ! ... in profiler AND also in Watt, and then also in lag !
Only in the profiler. The latter two points are straight up bullshit. 7µs are fully negligible in relation to the 100ms available step durations, both in terms of power consumption (Watt) and in terms of lag.
My stuff: Projects - Mods - Website

User avatar
Festus1965
Member
Posts: 4181
Joined: Sun Jan 03, 2016 11:58
GitHub: Festus1965
In-game: Festus1965 Thomas Thailand Explorer
Location: Thailand ChiangMai
Contact:

Re: mod LAG impact comparison - proofed data

by Festus1965 » Post

LMD wrote:
Wed May 18, 2022 09:37
Only in the profiler. The latter two points are straight up bullshit. 7µs are fully negligible in relation to the 100ms available step durations, both in terms of power consumption (Watt) and in terms of lag.
Interesting, how you can ignore facts !
* Video show rising Watt from just Ubuntu, then Minetest with minetest_game, less but it IS !
* compare Video with pipeworks+technic against Video without them and effect on htop, and so lag.
Human has no future (climate change)
If urgend, you find me in Roblox (as CNXThomas)

User avatar
runs
Member
Posts: 3225
Joined: Sat Oct 27, 2018 08:32

Re: mod LAG impact comparison

by runs » Post

Image

Could you check new Petz version? Now it includes a new forked mobkit engine (kitZ) what could be probably x3 fastest. Anyway more fastest than ever.

User avatar
runs
Member
Posts: 3225
Joined: Sat Oct 27, 2018 08:32

Re: mod LAG impact comparison

by runs » Post

I would like to know how ** 69.1 % / + 223 % load was reduced.

User avatar
Festus1965
Member
Posts: 4181
Joined: Sun Jan 03, 2016 11:58
GitHub: Festus1965
In-game: Festus1965 Thomas Thailand Explorer
Location: Thailand ChiangMai
Contact:

Re: mod impact comparison : petz - 4688047 / 28 days ago (~10.03.2022)

by Festus1965 » Post

runs wrote:
Sat May 28, 2022 10:03
I would like to know how ** 69.1 % / + 223 % load was reduced.
two posts will make another user happy I am sure ...
Festus1965 wrote:
Wed Apr 06, 2022 02:05
08.04.2022 - 6:25 - test server petz impact has started - finished 19:15 = near 11 hours
/status don't show any max_lag 0.09
/profiler save:
* petz : 69.1 %
* player_api: : 22.6 %
* fire : 8.3 %
why don't you just test yourself ?
the proportion should not change at all, whatever system you use
I made an about 1 hour fast test with

Code: Select all

-- from https://github.com/runsy/petz
print("[Mod] petz (d056120/28.05.2022)
/profiler:
* petz : 66.6 %
* player_api : 25.6 %
* fire : 7.2 %
= I see no basic for a new full 10-12 hour test ... as the higher player might just as of a problem I had after logged in, and needed more time to get profiler extract.

I see no speed up anyway, especial sure not a 3 times faster.
Human has no future (climate change)
If urgend, you find me in Roblox (as CNXThomas)

User avatar
runs
Member
Posts: 3225
Joined: Sat Oct 27, 2018 08:32

Re: mod impact comparison : petz - 4688047 / 28 days ago (~10.03.2022)

by runs » Post

Festus1965 wrote:
Sat May 28, 2022 12:01
runs wrote:
Sat May 28, 2022 10:03
I would like to know how ** 69.1 % / + 223 % load was reduced.
two posts will make another user happy I am sure ...
Festus1965 wrote:
Wed Apr 06, 2022 02:05
08.04.2022 - 6:25 - test server petz impact has started - finished 19:15 = near 11 hours
/status don't show any max_lag 0.09
/profiler save:
* petz : 69.1 %
* player_api: : 22.6 %
* fire : 8.3 %
why don't you just test yourself ?
the proportion should not change at all, whatever system you use
I made an about 1 hour fast test with

Code: Select all

-- from https://github.com/runsy/petz
print("[Mod] petz (d056120/28.05.2022)
/profiler:
* petz : 66.6 %
* player_api : 25.6 %
* fire : 7.2 %
= I see no basic for a new full 10-12 hour test ... as the higher player might just as of a problem I had after logged in, and needed more time to get profiler extract.

I see no speed up anyway, especial sure not a 3 times faster.
Wrong. 3% faster. This is just the beginning. More improvements will be made.

It IS your moral duty to take these tests. If you open Pandora's box, you can't disengage.

User avatar
runs
Member
Posts: 3225
Joined: Sat Oct 27, 2018 08:32

Re: mod LAG impact comparison

by runs » Post

Anyway, I have already told you many times that you are doing the tests wrong. Game tests with mods are done with the maximum mods possible, up to 250 max, I think.

So you can see the relative results. That 3% is multiplied x10 if Petz is run with other high performance mods, as the load is absorbed by the other demanding mods.

User avatar
runs
Member
Posts: 3225
Joined: Sat Oct 27, 2018 08:32

Re: mod LAG impact comparison

by runs » Post

In fact, I am going to create an official protocol for testing. In another new and unique post. And I will make my tests to show the world what is there and what is not, in a realistic and simple way.

User avatar
LMD
Member
Posts: 1386
Joined: Sat Apr 08, 2017 08:16
GitHub: appgurueu
IRC: appguru[eu]
In-game: LMD
Location: Germany
Contact:

Re: mod LAG impact comparison

by LMD » Post

runs wrote:
Sun May 29, 2022 06:57
So you can see the relative results. That 3% is multiplied x10 if Petz is run with other high performance mods, as the load is absorbed by the other demanding mods.
That still doesn't give 3x...
My stuff: Projects - Mods - Website

User avatar
jwmhjwmh
Developer
Posts: 125
Joined: Sun Jul 18, 2021 14:10
GitHub: TurkeyMcMac

Re: mod LAG impact comparison

by jwmhjwmh » Post

The tests don't say much if the server had no players/active blocks when data was being collected. To test petz, you should collect data with as many entities active as possible. You could keep these entities in a forceloaded area to ensure they remain active.

User avatar
jwmhjwmh
Developer
Posts: 125
Joined: Sun Jul 18, 2021 14:10
GitHub: TurkeyMcMac

Re: mod LAG impact comparison

by jwmhjwmh » Post

Also, you should compare the absolute average times, not the average percentages.

User avatar
Festus1965
Member
Posts: 4181
Joined: Sun Jan 03, 2016 11:58
GitHub: Festus1965
In-game: Festus1965 Thomas Thailand Explorer
Location: Thailand ChiangMai
Contact:

Re: mod LAG impact comparison

by Festus1965 » Post

bla bla bla ... yes do your own testing, but some of you always miss the starting post :
Festus1965 wrote:
Sat Apr 02, 2022 05:08
testing on empty world:
just engine 5.5.0 + mtg 5.5.0 run several times, some time, default options/settings
generated just standard area, mean near 125 Mapblocks (5*5*5), not moving gamer.

base is minetest game as 100 %

test with just one other mod, to see their impact On low part world, NO gamer in:
% of all used CPU time / rising load in % to basic config (100/(100 - tested mod %)) = + load
This mod impact test is about empty world, no nodes, no entities and no gamer to see the USELESS impact of a mod.
As MOST of the 350-400 server are most time empty - it makes sense and IS also a good start for basic research.

And you also forget that I have proofed my measurements on pipeworks and technic on my own active server.
As pipeworks and technic are using together even on an empty server 75.6 % of all load just on MTG (61.0 % in my tuned version) ... and then see how on my active server with still mod pipeworks and technic together are using ~55 % now, even most gamer already de-build their technic + pipeworks installation is TOO much, compare to techage running same time and IS USED active, but not reaches 1% at most extracts.

But this 55% are lower as the measurement actual there are also other mods taking part and reducing that % part, but NOT the real done useless work. 25% are just Top 20 other mods (wielded, poshud, postool, mobs_redo+++) that are not pipe/technic or from MTG.
Taking this 25% down, then 55% if from left 75% of real using server load without the others. So 55% of 75% == 73% might mean, just in my case tuned lag making mods (pipeworks + technic) there is just another 12% of this load that is from hoping REAL needed work on existing nodes and entities, where the other 61% are the useless impact this mods show even on an empty server as measured.

And again, how can it be, see the videos (25 gamer with, 27 gamer without) ... that without pipeworks + technic the % load of CPU thread is also halved down, as the measurements show also missing 55% of load with them ?

runs wrote:
Sun May 29, 2022 06:57
Wrong. 3% faster. This is just the beginning. More improvements will be made.

It IS your moral duty to take these tests. If you open Pandora's box, you can't disengage.

Anyway, I have already told you many times that you are doing the tests wrong. Game tests with mods are done with the maximum mods possible, up to 250 max, I think.

So you can see the relative results. That 3% is multiplied x10 if Petz is run with other high performance mods, as the load is absorbed by the other demanding mods.
You haven't understood anything, neither this thread testing mod against mod on empty server without their nodes/items, even %. It is testing the USELESS impact = USELESS not stopping basic lag.
Testing further your mod after this WRONG announcement ? lol - even not able to do this easy simple test yourself before ...

He also fails to read the first two posts ...
jwmhjwmh wrote:
Sun May 29, 2022 14:36
The tests don't say much if the server had no players/active blocks when data was being collected. To test petz, you should collect data with as many entities active as possible. You could keep these entities in a forceloaded area to ensure they remain active.

Then same I can do with petz and Mobs_redo:
Even on my active used server Asia Thailand Mobs_redo with the parts: monster 4.4 , sky, water, human 0.1 , npc, animal 2.4, fish 1.2, jellyfish 0.7, birds 0.1, birds 0.2, makes together about 9.1 % minimum of all, include whatever beside
100 % minus that same profiler extract as the mobs % (technic 38.5%, pipeworks 22.8 % and the other non MTG ~16.1 % (see 25% minus mobs 9.1 = 15.9) so we take 16%
all minus then 16 % as of other non MTG and 38.5 + 22.8 % = sum 77.3% load more then compare to a test.
Gives 22.7 % Rest is MTG and mobs_redo with ... from this 22.7 % the 9 % mobs is 33%.
Mean my server running without pipeworks, technic and all other mods, just with mobs would have 100% with 33% of it from Mobs_redo= 1/3.

Mobs_redo had on empty server WITHOUT any items, one time a bat ... an impact of 3%,
and now with real work the impact would b3 33% when working on a real world with animals, monster etc.

That is ok, when nothing to do should do nothing, but when there is work, I can understand the 33% also easier.

But compare to petz, petz is already using 69.1 %, maybe now 66% only on empty server, and I am sure thus USELESS lag making work will NOT get less in absolute numbers. It might not get much more with real dealing of existing animals (petz) on a real world,
but as seen at pipeworks + technic : there was even a rise of another 12 % ONTO the useless lag impact by pipeworks and technic also.
So I don't think that petz will be different there, maybe even more impact as of then ALSO have to deal with real existing entities.

So fact a real used mod mobs_redo plus ... is using about 33% load on an used world compare to only MTG load,
where petz starts already at 66 / 69 % on an empty, and when I remember one server even WITH pipeworks and technic petz had 33% of ALL.
Human has no future (climate change)
If urgend, you find me in Roblox (as CNXThomas)

User avatar
jwmhjwmh
Developer
Posts: 125
Joined: Sun Jul 18, 2021 14:10
GitHub: TurkeyMcMac

Re: mod LAG impact comparison

by jwmhjwmh » Post

Festus1965 wrote:
Mon May 30, 2022 01:06
bla bla bla ... yes do your own testing, but some of you always miss the starting post :
Festus1965 wrote:
Sat Apr 02, 2022 05:08
testing on empty world:
just engine 5.5.0 + mtg 5.5.0 run several times, some time, default options/settings
generated just standard area, mean near 125 Mapblocks (5*5*5), not moving gamer.

base is minetest game as 100 %

test with just one other mod, to see their impact On low part world, NO gamer in:
% of all used CPU time / rising load in % to basic config (100/(100 - tested mod %)) = + load
This mod impact test is about empty world, no nodes, no entities and no gamer to see the USELESS impact of a mod.
As MOST of the 350-400 server are most time empty - it makes sense and IS also a good start for basic research.

And you also forget that I have proofed my measurements on pipeworks and technic on my own active server.
As pipeworks and technic are using together even on an empty server 75.6 % of all load just on MTG (61.0 % in my tuned version) then see how with are still using ~55 % now, even most gamer already de-build their technic/pipeworks installation is TOO much, compare to techage running same time and IS USED not reaches 1% at most extracts.

But this 55% are lower as the measurement actual there are also other mods taking part and reducing that % part, but NOT the real done useless work. 25% are just Top 20 other mods (wielded, poshud, postool, mobs_redo+++) that are not pipe/technic or from MTG.
Taking this 25% down, then 55% if from left 75% of real using server load without the others. So 55% of 75% == 73% might mean, just in my case tuned lag making mods (pipeworks + technic) there is just another 12% of this load that is from hoping REAL needed work on existing nodes and entities, where the other 61% are the useless impact this mods show even on an empty server as measured.

And again, how can it be, see the videos (25 gamer with, 27 gamer without) ... that without pipeworks + technic the % load of CPU thread is also halved down, as the measurements show also missing 55% of load with them ?

runs wrote:
Sun May 29, 2022 06:57
Wrong. 3% faster. This is just the beginning. More improvements will be made.

It IS your moral duty to take these tests. If you open Pandora's box, you can't disengage.

Anyway, I have already told you many times that you are doing the tests wrong. Game tests with mods are done with the maximum mods possible, up to 250 max, I think.

So you can see the relative results. That 3% is multiplied x10 if Petz is run with other high performance mods, as the load is absorbed by the other demanding mods.
You haven't understood anything, neither this thread testing mod against mod on empty server without their nodes/items, even %. It is testing the USELESS impact = USELESS not stopping basic lag.
Testing further your mod after this WRONG announcement ? lol - even not able to do this easy simple test yourself before ...

He also fails to read the first two posts ...
jwmhjwmh wrote:
Sun May 29, 2022 14:36
The tests don't say much if the server had no players/active blocks when data was being collected. To test petz, you should collect data with as many entities active as possible. You could keep these entities in a forceloaded area to ensure they remain active.
You are mainly measuring very short globalstep durations. When put under stress, mods may have very different performance characteristics. The information you give can only be used for optimizing performance on empty servers, not performance in general. My point is that runs should not spend much time optimizing his mod based on this data. He should collect performance information when petz is simulating many entities.

User avatar
Festus1965
Member
Posts: 4181
Joined: Sun Jan 03, 2016 11:58
GitHub: Festus1965
In-game: Festus1965 Thomas Thailand Explorer
Location: Thailand ChiangMai
Contact:

Re: mod LAG impact comparison

by Festus1965 » Post

runs wrote:
Mon Apr 11, 2022 18:12
Anyway I am not going to stand still, I have reviewed my Petz code and I can make 3 major performance optimizations. With it I will be able to reduce 30%-40% of the load according to my estimations.

I'm going to get to work.
runs wrote:
Sat May 28, 2022 09:38
Image

Could you check new Petz version? Now it includes a new forked mobkit engine (kitZ) what could be probably x3 fastest. Anyway more fastest than ever.
are you sure how to calculate % ? Why have you deleted the x3 faster ? haha

The short test was NOT 3% less impact, but also not 3% faster !
69.1 % - 66.6 % (just short test) = 2.5 %points
OR 3.6 % less (2.5 of 69.1) then older version.

so
* mobs :
** first choice is mobs_redo with belonging mobs with just + 3.3% load,
** before next animalia (+needed creatura) + 95% load (double lag)
** not recomended: petz with raising 223% load (tripple lag) ... maybe for fast and strong servers only
to get just better then animalia, and get 2nd place maybe the impact need to be under 48.7 %.
Mean you have to loose more than 20.4% points, or speed up near 30% that there will be a change.

But even then I recommend still mobs_redo ... clear the better programming to avoid useless load (= useless lag),
as also shown from techage against pipeworks and technic.
Human has no future (climate change)
If urgend, you find me in Roblox (as CNXThomas)

User avatar
Festus1965
Member
Posts: 4181
Joined: Sun Jan 03, 2016 11:58
GitHub: Festus1965
In-game: Festus1965 Thomas Thailand Explorer
Location: Thailand ChiangMai
Contact:

Re: mod LAG impact comparison

by Festus1965 » Post

jwmhjwmh wrote:
Mon May 30, 2022 03:18
You are mainly measuring very short globalstep durations. When put under stress, mods may have very different performance characteristics. The information you give can only be used for optimizing performance on empty servers, not performance in general. My point is that runs should not spend much time optimizing his mod based on this data. He should collect performance information when petz is simulating many entities.
your kidding me ?
exact this I have done in that post already with
* pipeworks + technic on my real server even using MORE % then the empty useless lag run
... empty test 61.9 - 67.1 % against 75% usage on AsiaThailand (to base MTG) under normal daily conditions (even more usage !)

* and also at mobs_redo compare to 3% empty, and about 33% load on running server with entities.
... as empty 3% impact against 33% impact on AsiaThailand (to base MTG), gain 30%(poins) or multiplicate by 11 when working WITH real entities, but this is sure still less then a working petz I guess.

* advtrains test was 93.7 - 93.8 %, and on https://pandorabox.io/index.php/Profiler-23102019 you get
1. - 31.5 % = advtrains
2. - 13.2 % = mesecons
3. - 10.6 % = pipeworks
4. - 9.3 % = technic
5. - 7.0 % = advtrains_train_japan
6. - 3.7 % = pandorabox_costum
7. - 2.9 % = advtrains_subway_colored
8. - 1.9 % = advtrains_train_steam
9. - 1.7 % = mobs_monster
10. - 1.1 % = default
taking the other mods % away (13.2, 10.6, 9.3, 3.7, 1.7 = 38.5) guess 40% are not adv... or MTG
mean 31.5 % ONLY advtrains of 100%, is then how much part of left 60% ? = 52.2 % of all load,
in this case is seam to be less impact as on an empty server, wow but double the basis mtg lag is already a big number
if taking then all together 31.5 + 7 + 3.7 + 2.9 + 1.9 = 47% of left 60% = 78.9 % part of all load with just MTG, mean multiplicate the basic lag still by 5, or adding ~400%.

Do you really think petz will have LESS impact when have to work with real petz on real server ?
nice dream ... to beat faster animalia or even less impact mod mobs_redo+++ there have to be much more change, I am sure.

Make some server admins give me profiler extracts running petz ... then we can see it better.
Human has no future (climate change)
If urgend, you find me in Roblox (as CNXThomas)

Post Reply

Who is online

Users browsing this forum: No registered users and 15 guests