Difference between revisions of "Solo Act"
(→Assignment 2) |
(→Assignment 2) |
||
| Line 25: | Line 25: | ||
Parallelize | Parallelize | ||
| + | One of the immediate problems I realized with this project was that the target functions were far too large. Parallelization would require possibly three or more kernels, which was beyond the scope of this assignment. Instead I decided to focus on the bsp tree portion of the code, and decouple this portion from actual dungeon generating logic. | ||
| + | [[File:Sourcedecouple.png|500px]] | ||
| + | The decoupled source-code can be seen above, along with the timing logic in it's respective main function. | ||
[[File:Mytreedia.png|500px ]] | [[File:Mytreedia.png|500px ]] | ||
| + | To parrellize a bsp tree required some analysis which can be seen above. | ||
[[File:Warpss.png|500px]] | [[File:Warpss.png|500px]] | ||
| + | The image above reflects the design I chose with respect to the warps and thread behavior. | ||
[[File:Outputgood.png|500px]] | [[File:Outputgood.png|500px]] | ||
| − | |||
| Line 44: | Line 48: | ||
| − | + | ||
Revision as of 18:44, 13 April 2018
Contents
Solo Act
Team Members
- Nick Simas, All of the things.
Progress
Assignment 1
Profile
For assignment 1, I selected an open-source dungeonGenerator project from github.
https://github.com/DivineChili/BSP-Dungeon-Generator/
As you can see from the above images, the purpose of this program is to generate a map image for game content. The program achieves this by repetitively splitting a 2d space using a binary partition algorithm.
The project was written for windows, so I decided to initially profile with the built in Visual Studio profiler.
The above image shows the function inclusive time percentage. The results are 22% and 15% respectively. The only entries higher are Main and library components used for printing. This demonstrates that the majority of source code processing is occurring in these two functions. Both of them would thus are hotspots and may benefit from parallelization.
Assignment 2
Parallelize
One of the immediate problems I realized with this project was that the target functions were far too large. Parallelization would require possibly three or more kernels, which was beyond the scope of this assignment. Instead I decided to focus on the bsp tree portion of the code, and decouple this portion from actual dungeon generating logic.
The decoupled source-code can be seen above, along with the timing logic in it's respective main function.
To parrellize a bsp tree required some analysis which can be seen above.
The image above reflects the design I chose with respect to the warps and thread behavior.
Assignment 3
Optimize
