MOA333 wrote:
| did you saw the tests?
| the full recursive checkSums is taking 60% and more of CPU time
| on 256*256
|
| Do you think we can do somethink about this?
We could very easyly remove it, but this would make the desynchronisation
bugs harder to find. All this CPU is used into Map, Sint32
checkSum(bool heavy);
when heavy=true. I think that we'll add an option to enable/disable it.
| (still the gfx on 128*128 but there i have lmess than 50% of cpu load so
| i guess it dosent matter)
I'd like to know the cpu you made thoses tests on. Especially what are
the size of the cache (level 1 and 2) of you cpu.
| why it is so big diference betwen 128*128 and 256*256?
Because some computing is propostional to the surface of the map.
The gradient system is, and Map::checkSum(heavy) is when heavy=true.
And a 256x256 map is *four* time bigger than a 128x128, so if thoses
computation time are the mosr important, it is 4 times slower!