"Ticking Problem"

[TommyB]

Estimate of Province Data:

I am going crazy and using 64 bit for everything except race/profession.

- 1 byte for race
- 1 byte for profession
- 20 * 8 byte for buildings + barren + total land
- 30 byte province name
- 30 byte ruler name
- 3 * 8 byte for gold, food, runes
- 4 * 8 byte for soldiers, def spec, off spec, elites
- 2 * 8 byte for thieves and wizards

= 294 byte

All other values should be calculated, maybe I miss something.

This means for 10k Provinces the data that needs to be updated
amounts to ~3MB.

Q: Why does it take 2+ minutes to update 3MB of data ?

[moe]

I dont know, but I find it hard to believe that all the data is just 3MB...

[moe]

might have something to do with amount of files too. I once copied 15k guitar pro tabs from one folder to another, and even though each file is like 50kb, it took ages :P

[Main]

It's not that easy. If only 1 little bit of code is wrong, The code will try to update and it dosent work. That will then bounce back and it will try to do it again. So what happens is that you have 1 tiny bit of information that will bounce back and forth demanding a **** load of computer power.

[Luc]

If speed only depended on total size, ticking would not have been a problem

[macsean]

It wasn't a problem with 100,000 people. Why would it be with 10,000?

[TommyB]

I left out stuff like kingdom relations etc. but really that shouldnt make a big difference.

Calculating the data should take even less time, so really.. where does all the time go ?

My best bet is that they are sending 10k badly optimized sql statements to the dbms, which is of course much slower than just writing all data away in text files.

Player and kingdom data is stored as Delphi records serialized into text files (i.e., there is no DBMS).

[macsean]

My guess is the CMs do the update calculations with a calcualtor and update them manually themselves.

[Luth]

anyone have an abacus? or comptometer?