Hi,
The theory regarding database contention on the food field, and therefore its corresponding table is very plausible.
Evony, give us less upkeep for now, but ensure it's not zero. Based on the hypothesis, the lag should then stay, as the records would still need to be updated at the same rate; only by a lesser amount.
If the lag remains, look at splitting the table holding the food field into more than one table. Split it in two say, and put locations with odd X-coordinates in one table, and locations with even X-coordinates in another. If the lag comes down by approximately half, you're onto a solution. Scale until there are diminishing performance returns...
Assuming you are using a database that can do partitioning, place the split up table on different physical disks to reduce disk contention.
Regards,
ObelixMMIX




Gooooo evony team!

Bookmarks