Time Nick Message 11:42 Bombo helo 11:43 Bombo i found the language setting in minetest 5.4.0, set it from nothing (english) to de (german) restarted it, but it still is englsh 11:43 Bombo are the locales not included in the android version? 11:43 Bombo did i mention amdroid? android ;) 11:44 sfan5 android currently does not come with language support 11:44 Bombo no 5.4.1 version either 11:44 Bombo ok sfan5 11:45 Bombo probably nothing changed for android in the .1 i guess 11:47 sfan5 even if you had 5.4.1 it still wouldn't work, yea 12:12 Bombo no i mean genera 0 and enable verbose output it'll print the profiler 20:32 sfan5 there should be a "Server: map saving (sum)" entry which tells you how long map saving took 20:33 whosit I did another thing: 20:33 whosit moved players.sqlite file to ramfs directory and symlinked it, and spike was gone 20:34 whosit "map saving" time will show how long it took to rewrite players.sqlite? 20:34 sfan5 map saving *and* player data saving 20:35 whosit ok... I will try to measure it that way then. Still not sure how to better get rid of it :) 20:36 entuland this seems important if it made a difference: "moved players.sqlite file to ramfs directory and symlinked it, and spike was gone" 20:37 whosit and I see same spike on a server that's using postgres backend and has no players.sqlite 20:40 entuland can't tell about postgres, but if the problem disappeared by changing the file location and symlinking it, since it should be transparent to minetest, that seems to point at something else interfering with that IO 20:42 whosit it's not just location though, I have moved file to a memory filesystem - so no slow IO when writing it 20:42 whosit (linux ramfs) 20:44 entuland that's the thing, even writing the entire file at once every time the amount of data is risible and doesn't justify the entire gameserver freezing 20:45 sfan5 is the disk a HDD? 20:46 whosit on my test machine, yes, on the postgres backed one - idk 20:46 whosit lag seems about the same on both 20:48 whosit I notice this periodical spike only with xp_redo enabled, not other mods - that's the strangest thing. But it may be explainable by constant metadata change... 20:50 entuland I would try and narrow down that thing by doing a small mod that only touches the meta at that same interval 20:51 entuland it may as well be something done by hooks.lua 20:51 entuland which is the line run right after touching the meta 20:52 entuland that hook goes on to run all the functions hooked by register_hook 20:53 whosit tried commenting it out - makes no difference 20:53 entuland good 20:53 entuland commenting the meta touch out gets rid of the issue I guess? 20:53 whosit yes, set_int() removes the lag spike 20:54 whosit *commenting it out 20:54 entuland ok 20:55 entuland maybe the profiler data will give more clues 21:06 whosit https://pastebin.com/TZn8Q1k8 <- map saving from debug.txt 21:09 sfan5 writing some stuff to disk certainly shouldn't take 500ms 21:10 sfan5 you might also want to look at this setting https://github.com/minetest/minetest/blob/stable-5/minetest.conf.example#L1512-L1514 21:15 whosit setting sqlite_synchronous = 0 (OFF) gets rid of lag spike (map saving is up to 8ms with 6 clients) 21:17 sfan5 hope you read the warning about corruption in the docs 21:18 whosit yes. 21:21 whosit setting it to 1 (NORMAL) gives same 5-second-period ~500ms spikes 21:22 whosit default is 2 I assume... so normal option works same as full sync 21:30 entuland crabs... to times that my desktop rebooted without any error or reason whatsoever today 21:31 entuland s/to/two 21:33 whosit :( never happened before? 21:36 whosit so, what should I do? make a minimal mod to reproduce the spike? 21:50 MTDiscord No idea sorry, out of power to even try googling 21:51 MTDiscord At least seems like it was power grid hiccups here and not my PC going nuts 21:53 MTDiscord The fact that sqlite misbehaves in one mode on the normal disk, stops misbehaving changing that mode, and stops also going to ramfs, the issue could be more tied to the FS / sqlite manager / driver or whatever than being on minetest itself 21:55 MTDiscord Although the fact that the issue happens on postgres as well would not match (unless for some reason the culprit affects posgres as well somehow) 22:00 MTDiscord you have a dead sector on disk 22:14 whosit 1. the spike issue happened on another machine 2. I re-created server from scratch using /mods list, and issue appeared on my local machine too 22:14 whosit only common thing - xp_redo mod 22:16 whosit server is using completely different config, I don't even have direct access to it to see how postgres is set up, etc. 22:17 whosit but we did make sure that spike issue disappears from server too, when xp_redo is disabled 22:22 whosit real server should have bigger player db, but if it's using postgres and values change only for ~10 test clients, that still does not make sense 22:29 AntumDeluge The API shows me how to unregister items (craftitem & node), but I don't see any method for unregistering ores. Can it be done? Or, is it necessary to unregister ores if I am replacing an ore-bearing node? 22:34 calcul0n_ AntumDeluge, ores are just nodes like others, i guess you do it the same way 22:44 AntumDeluge calcul0n_, interesting. I called "core.unregister_item(item_name)", but I find that it is still stored in "core.registered_ores". 22:52 calcul0n_ ho, i forgot about register_ore(), i don't know what happens if you unregister the corresponding node then 22:53 AntumDeluge Maybe I just need to do "core.registered_ores.ore_hash = nil". Or maybe I just leave it alone as maybe it isn't necessary to unregister ores. 22:58 calcul0n_ i'd try the second first but that's a shot in the dark :)