Tweet
Mir Vengeance Admin — 07:20 UK morning
-
-
Mir Vengeance Admin — 07:21 UK not good. Man down <@311909666961489921> you will be missed. Lets see what caused it this time.Comment
-
Mir Vengeance Admin — 07:32 UK The world was hitching the whole time. From 22:50 to 23:30 there were 439 ticks of 150ms or more. The worst were 1.4 to 4.7 seconds, and none of that time was SQL. One tick spent 4.7 seconds in object processing and only got through 7 objects. Several others spent about 1.4 seconds just reading players, so the monsters barely ran that tick. Coxy's "lags brutal" at 22:53 sits on top of that.Comment
-
Mir Vengeance Admin — 07:54 UK Last night’s log shows it plainly: A new glyph on Mana froze the server for about a second, over and over. Picking up a new item was saving the entire bag. CyanoGhast’s kill on Red Cave took 4.4 seconds inside that one monster. A spell on the same map took 2.9 seconds. The death was saving the character and every dropped stack before the tick could move on. Every five minutes, at about :38, the scheduled save did the same thing for one character and added another hitch of about 0.8 seconds.Comment
-
Mir Vengeance Admin — 08:59 UK Congrats on the Evil Mir kill last night guys. Shame you left 3 items on the floor ????Comment
-
Mir Vengeance Admin — 09:03 UK So have worked out that the user item logs - Website to see who owns what, is already at 4gigs its been 12 days! it has 4 million rows ???? 418,000 items. I have removed all pots and scrolls and common and below from writing to this table, currently removing all the crap from log database now. This reduction is writing to the database should help towards reducing the "lag"Comment
-
I AM THORRRRR — 09:16 UK Is the bag save part of the logging or core character save mechanism?Comment
-
Mir Vengeance Admin — 09:21 UK 2 different things, so its saves to your bag then its write to the log table. So each item drops writes to an almost pointless table. Its a great feature to have on the website, but now with the amount of players and stuff, it needs to be stripped back. Worst case I remove it fully and do a weekly dump instead, but I am not at that stage yetComment
-
I AM THORRRRR — 09:23 UK OK, so perhaps we need to look at this slightly differently. We can still have the website functions but need to do it in a clever wayComment
-
I AM THORRRRR — 09:23 UK The server files. Are they original ones or have you altered themComment
-
Mir Vengeance Admin — 09:27 UK Purged from live ItemTrace ~2.68M pots / scrolls / books / food / amulets + durability ticks ~159k bait / fishing junk ~718k periodic Persisted save rows Result Before After Rows 4,050,390 ~492,000 Size ~4.2 GB ~508 MBComment
-
Mir Vengeance Admin — 09:59 UK digging through the code, and logs Found some pretty stupid bugs. Bag refresh being sent twice! - now changed to only send refresh once. Every pot used was writing to SQL - debugging logs - now removed. Pot/scroll uses drops and usage now longer being written to the log table - Huge amount of data no longer needed to be added to the database table.Comment
-
I AM THORRRRR — 10:04 UK Let's see if that frees up some stuff. If not. I will pm you and go through some ideasComment
-
Reina — 10:04 UK we could also do w/o the weather, especially the fog and rain inside caves (for some reason). ppl playing mir are no longer spring chickens..no need to ruin our eye sight even more lol. besides..the fpg makes me dizzy-.-Comment
-
Redmoonevil — 10:04 UK STKR wasnt to bad this morning and i was hammering itComment
Comment