Long #repop and zone times after source upgrade

**Akkadius** · #1 02-06-2015, 05:53 PM

I know you said everything is set to 0, but do you even have quests set to 0?

If you're getting that size of quest messages your file writing is going to slow you down big time

Bohbo · #2 02-06-2015, 06:01 PM

Quote:

Originally Posted by Akkadius

I know you said everything is set to 0, but do you even have quests set to 0?

If you're getting that size of quest messages your file writing is going to slow you down big time

I literally have every field in the log control table set to 0 and restarted the server.

In North Karana I get a 12 sec repop time.

**Akkadius** · #3 02-06-2015, 06:12 PM

Quote:

Originally Posted by Bohbo

I literally have every field in the log control table set to 0 and restarted the server.

In North Karana I get a 12 sec repop time.

If you are compiling with VS2013 ultimate, you can profile your zone process while you are repopping and figure out what is chewing up CPU cycles by taking so long

Bohbo · #4 02-06-2015, 06:55 PM

Quote:

Originally Posted by Akkadius

If you are compiling with VS2013 ultimate, you can profile your zone process while you are repopping and figure out what is chewing up CPU cycles by taking so long

VS is still installing. Keep in mind all logging is off but it seems like i am getting a hard disk write spike during repop. The spike goes to about 350kb/s not very high but it sustains through the repop. The moment a mob shows up the spike drops. CPU doesn't seem to change.

**Akkadius** · #5 02-06-2015, 07:03 PM

Quote:

Originally Posted by Bohbo

VS is still installing. Keep in mind all logging is off but it seems like i am getting a hard disk write spike during repop. The spike goes to about 350kb/s not very high but it sustains through the repop. The moment a mob shows up the spike drops. CPU doesn't seem to change.

OK, then what is being written when you open up resource monitor

Bohbo · #6 02-06-2015, 07:09 PM

Quote:

Originally Posted by Akkadius

OK, then what is being written when you open up resource monitor

mysqld.exe is the culprit it looks like. Still trying to write with logging disabled somehow?

**Akkadius** · #7 02-06-2015, 07:12 PM

Quote:

Originally Posted by Bohbo

mysqld.exe is the culprit it looks like. Still trying to write with logging disabled somehow?

If it is truly mysql, then while you repop do a:

#logs gmsay 36 1

And you can get an idea of what queries are trying to write.

You shouldn't be pushing MB/s of data on write