Open main menu

CDOT Wiki β

Changes

GPU610/Cosmosis

769 bytes added, 13:21, 2 February 2013
Assignment 1
All of these profiles where were ran for about 4 to 5 minutes each. It seems that when the body count is low (1000) the program spends most of its time in the '''addforces()''' function, which is a user defined function within one of the source files. However, when the body count gets higher, it seems that the program slows down so much from having to draw all of the bodies, it spends most of its time in the Java defined'''fillOval()''' function, rather than the '''addforces()''' function. I'm not entirely sure if we would be able to parrallelize that function, since it is in a library. It may be possible to simply define a function that does the same thing and put it in the program.
=====Example Profiles of Barnes Hut Algorithm=====
When run with 10000 bodies:
[[File:10000_bodies_BH_profile.PNG]]
 
 
When run with 25000 bodies:
[[File:25000_bodies_BH_profile.PNG]]
 
 
When run with 50000 bodies:
[[File:50000_bodies_BH_profile.PNG]]
 
 
All of these profiles were ran for about 5 minutes each. The percentage of time the program spends in all of the functions is pretty consistent. Again, the Java defined '''fillOval()''' function is taking the longest amount of time. I'll have to look into adding that function into the main class. Although the '''updateForce()''' and '''insert()''' functions combined take over 25% of the execution time, so something can be done about that.
 
If someone knows how to add spoiler tags, it would be much appreciated if you could add them to my 2 groups of pictures.
=== Assignment 2 ===
=== Assignment 3 ===
1
edit