Timeout when zoning

[sesmar]

Originally Posted by Angelox

Trick is, how do you figure out what is the loot in use, and what is not, so it can be removed?

This query will tell you all Loottables that are not assigned to a NPC.

SELECT
  npc_types.id,
  lootdrop.id
FROM
  npc_types
  RIGHT JOIN lootdrop
    ON lootdrop.id=npc_types.loottable_id
WHERE
  npc_types.id IS NULL

Warning this query will take a little bit of time to run, for some reason MySql does not like right joins looking for nulls but it will work and will give you the desired information.

[bufferofnewbies]

Hey, it actually wasnt a dbase error.

It was an MySQL error. I reloaded the drivers, apparently one was corrupted as was causeing an error in packet sending. Once I reloaded them (not sure which one, as I just did them all due to lack of time.), most zones times take about as long as a sneeze again. Of course, my dBase probably DOES need an enima with all the extra stuff in it.

ODBC Driver.exe for the win!

So anyone who is having this problem with something like Angel's dBase (since he usually optimizes his pretty well), try reloading MySql drivers.

[fathernitwit]

loot is stored in shared memory, it is not loaded at zone boot, so that is not your problem.

[bufferofnewbies]

I dont believe my error was about loot
It was about packets not being sent to players at all.
For some reason, whenever they zoned it simply stopped acting upon them.

but then again, I don't really know what all is being done. It could be anything.
All I know is.. The only thing i have changed so far is mysql and now the problem is solved.

[John Adams]

FNW, what's in the Zone debug logs is slightly confusing then:

[10.30. - 16:14:00] [ZONE__INIT] Loading server configuration..
[10.30. - 16:14:00] [ZONE__INIT] Log settings loaded from log.ini
[10.30. - 16:14:00] [ZONE__INIT] Connecting to MySQL...
[10.30. - 16:14:00] [ZONE__INIT] CURRENT_ZONE_VERSION: EQEMu 0.7.0
[10.30. - 16:14:00] [ZONE__INIT] Log settings loaded from ./log.ini
[10.30. - 16:14:00] [ZONE__INIT] Mapping Incoming Opcodes
[10.30. - 16:14:00] [ZONE__INIT] Loading Variables
[10.30. - 16:14:00] [ZONE__INIT] Loading zone names
[10.30. - 16:14:06] [ZONE__INIT] Loading items
[10.30. - 16:14:06] [ZONE__INIT] Loading npc faction lists
[10.30. - 16:14:06] [ZONE__INIT] Loading loot tables
[10.30. - 16:14:06] [ZONE__INIT] Loading guilds
[10.30. - 16:14:06] [ZONE__INIT] Loading factions
[10.30. - 16:14:06] [ZONE__INIT] Loading titles
[10.30. - 16:14:06] [ZONE__INIT] Loading AA effects
[10.30. - 16:14:06] [ZONE__INIT] Loading swarm spells
[10.30. - 16:14:06] [ZONE__INIT] Loading tributes
[10.30. - 16:14:06] [ZONE__INIT] Loading corpse timers
[10.30. - 16:14:06] [ZONE__INIT] Loading commands

This looks like the Items and Loot Tables are loaded into each zone -- tho the memory usage makes me think differently. Wouldn't zone mob loot table be unique to that zone only? Maybe this is getting off topic. Sorry.

[cbodmer]

World does load items into shared memory, but I don't think it does loottables and lootdrops, that wouldn't make much sense. I am not sure what the items are the zone is loading...

-Chris

[cbodmer]

Looking through the code, I was wrong. Seems like everything the zone needs is coming via shared memory. However I am not sure whether everything is actually preloaded by world or whether loot data is preloaded on first use.

-Chris

[Angelox]

Also, it probably would be a good idea to look for ways to speed up your MySQL server, I still think the further we enhance the zones, slower loading times are unavoidable - If you stop and think, most people have it all in one machine; Client , server, MySql, etc. And probably peak usage for MySQL is during zone-loading, as is for client and EqEmu.
I don't think differences are really that great; "autobootup_timeout(60000)", and "CLE_keepalive_timer(65000)", was way too high for me, but I kept the number, because I like the extra "buffer" time.
I think if FNW can figure out a way to include a setting in the eqemu_config.xml file (as per cbodmer), so anyone could make this adjustment, would solve a lot. It probably would not be a bad idea to keep the default setting to something long like "autobootup_timeout(60000)", and "CLE_keepalive_timer(65000)", unless this somehow affects other performance.