D
deleted
Guest
deleted
Last edited by a moderator:
The M'Hael
Chieftain
- Joined
- Jan 4, 2007
- Messages
- 86
Looks like I was the one misunderstanding. Ignore this post...
Iustus
King
It is possible to do a build which allows you to generate a log of what functions are taking how much time. It generates a enormous amount of data, it takes some work to sift through it to what is important and what isnt.
I could do such a build, if someone who is good at manipulating logs of data into useful information wants to take a go at it. It is a non-trivial task, particularly because it is not always obvious what is taking a long time because waiting on the human and what is taking a long time because it takes a long time.
-Iustus
D
deleted
Guest
deleted
Last edited by a moderator:
Iustus
King
That is precisely what I am talking about. It is called 'code profiling', and I can do a build with it turned on. But as I said, it generates an enormous amount of data, someone has to commit to sifting through it, or I am not going to post such a build.
Blake and I have looked at the data from it from time to time, but not in great detail.
-Iustus
D
deleted
Guest
deleted
Last edited by a moderator:
Iustus
King
The code was not written for speed. Take one look at it and there are a ton of optimizations that come to mind to speed things up. However, the biggest gains often involve the biggest changes.
I think I deleted my last log, I will see about making a new log and posting a bit of it so you can see what it looks like.
-Iustus
D
deleted
Guest
deleted
Last edited by a moderator:
D
deleted
Guest
deleted
Last edited by a moderator:
gnome
Warlord
I don't know how relevant this is, but one item that I've noticed (playing vanilla civ) is AI unit patrolling. Not specific to Better AI, of course, but a definite slowdown between turns.
Does this benefit the AI in any respect rather than having unused units sit still? If not, a lot of time could be saved, that could be used for AI computations without annoying the human player so much.
Does this benefit the AI in any respect rather than having unused units sit still? If not, a lot of time could be saved, that could be used for AI computations without annoying the human player so much.
D
deleted
Guest
deleted
Last edited by a moderator:
Iustus
King
Today's build (building as we speak) will have profiling enabled (in both versions). It actually should have always been enabled in the assert version. (You should test with the non-assert version to get more accurate numbers).
Hold down ctrl-shift-alt-D and you will get the debug menu (you need chipotle enabled):
Go to the profile tab, and turn on profiling for the DLL.
Every turn, the file "dllprofile.txt" in your "My Games\Warlords\Logs" directory will get another turn's worth of data.
You are going to want to use something like excel to make sense of the data.
Enjoy,
-Iustus
Hold down ctrl-shift-alt-D and you will get the debug menu (you need chipotle enabled):
Go to the profile tab, and turn on profiling for the DLL.
Every turn, the file "dllprofile.txt" in your "My Games\Warlords\Logs" directory will get another turn's worth of data.
You are going to want to use something like excel to make sense of the data.
Spoiler this is what the data looks like :
rocessTechEnjoy,
-Iustus
D
deleted
Guest
deleted
Last edited by a moderator:
Iustus
King
Go download the 1/29 build (not the assert one, the previous build), this is a direct link to the warlords version
The time number is total time, the sum of every call. Divide the "Time" by "Num" to get the "Ave" (average) time one call of the function. Realistically though, the total Time number is just as important, if not more important. A quick function that is called a million times could be more important to optimize than a long function that is only called once.
-Iustus
D
deleted
Guest
deleted
Last edited by a moderator:
primem0ver
Emperor
Thought this might be of significant interest to this topic:
I did my own "profiling" by adding text to a custom log file (windows up time is posted at the begining of each line). I did this because I am working on a major addition to the game and I was curious as to why my turns started taking so long at a given point in the game. Here is what I discovered:
AI_explore() is used by all exploring AI units when the preceding calls (in AI_ExploreMove() and AI_ExploreSeaMove()) do not push a mission.
THIS METHOD IS EXTREMELY TIME CONSUMING in terms of computer time needed.
This method, when called on a huge map can take as long as 5 seconds PER UNIT!
The reason it does not usually create a problem is because it is not called very often. But I had 3 enemy units behind my lines during peace time (Triremes) which must go along coast. Because they could not explore, attack, or do anything else, these calls were taking 15 seconds per turn!
If you look at the code it is pretty easy to understand why the code takes so long. It cycles through every plot on the map to find the next best area to explore.
I am working on a new method to replace this one but I have to put it aside for now because I have other commitments (and I just decided to remove the units, lowering turn times from 30 to 10 seconds!) to my current project now that I know that it is not the problem!
Anyway... this might be something worth looking into and if anyone wants to help me when I am ready, I could use it. A new approach to finding explorable territory will not be easy even though I have an approach in mind.
I did my own "profiling" by adding text to a custom log file (windows up time is posted at the begining of each line). I did this because I am working on a major addition to the game and I was curious as to why my turns started taking so long at a given point in the game. Here is what I discovered:
AI_explore() is used by all exploring AI units when the preceding calls (in AI_ExploreMove() and AI_ExploreSeaMove()) do not push a mission.
THIS METHOD IS EXTREMELY TIME CONSUMING in terms of computer time needed.
This method, when called on a huge map can take as long as 5 seconds PER UNIT!
The reason it does not usually create a problem is because it is not called very often. But I had 3 enemy units behind my lines during peace time (Triremes) which must go along coast. Because they could not explore, attack, or do anything else, these calls were taking 15 seconds per turn!
If you look at the code it is pretty easy to understand why the code takes so long. It cycles through every plot on the map to find the next best area to explore.
I am working on a new method to replace this one but I have to put it aside for now because I have other commitments (and I just decided to remove the units, lowering turn times from 30 to 10 seconds!) to my current project now that I know that it is not the problem!
Anyway... this might be something worth looking into and if anyone wants to help me when I am ready, I could use it. A new approach to finding explorable territory will not be easy even though I have an approach in mind.
