search

mulander / evolutionchamber

Automatically exported from code.google.com/p/evolutionchamber
0 stars 0 forks source link

Cached Merge / Keep track of current waypoint index #161

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Cached the getMergedState and added a index to keep track of what waypoint the 
evaluation was currently at.

Noticed a 50% increase in games per second for waypoint builds.

Original issue reported on code.google.com by nafets...@gmail.com on 25 Nov 2010 at 4:39

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by netpr...@gmail.com on 25 Nov 2010 at 6:48

GoogleCodeExporter commented 8 years ago 
Applied the patch and it works better then advertised :)
We need to compare the g/s between release 0022 and 0023 when it's ready for a 
release in order to get the cumulative performance gain from all the patches in 
the changelog.

Fixed in r138

Original comment by netpr...@gmail.com on 25 Nov 2010 at 6:58

GoogleCodeExporter commented 8 years ago

Original comment by netpr...@gmail.com on 26 Nov 2010 at 10:06

GoogleCodeExporter commented 8 years ago 
I did some speed tests to look at how much this patch improved performance.  
Using the two different kinds of tests that netprobe used in  issue 158  (one 
with and one without waypoints), I calculated the average games played per 
second with two different versions of the application (before and after the 
patch).  The two tests are described below.

Before running each test, I deleted the "etc" directory and restarted Evolution 
Chamber to avoid caching or memory issues that might effect performance.  Each 
test used 1 processor and ran for 20 seconds.  The average games played per 
second was calculated using code that I added to the application.  I didn't 
check the resulting build order for accuracy...I only focused on the speed.

Test 1:
Final: 7 Mutas, +1 Flyer Attack

Test 2:
WP0: 6 Zerglings
WP1: 6 Roaches
WP2: 2 Hydralisks
WP3: 3 Overseers
Final: 7 Mutalisks, +1 Flyer Attack

==========

Before patch (r137):
Test 1: 2263.6097935814796
Test 2: 2751.724211543719

After patch:
Test 1: 2498.2067605795696 (~9% increase)
Test 2: 3724.5669481423683 (~36% increase)

Original comment by mike.angstadt on 29 Nov 2010 at 11:24

GoogleCodeExporter commented 8 years ago 
nafets.st, there appears to be a problem with the patch:

http://code.google.com/p/evolutionchamber/source/detail?r=138

Original comment by mike.angstadt on 29 Nov 2010 at 11:49

GoogleCodeExporter commented 8 years ago 
Thank you for noticing this error, I'm looking into it currently.

Original comment by nafets...@gmail.com on 30 Nov 2010 at 1:10

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Accidentally deleted post.

Original comment by nafets...@gmail.com on 2 Dec 2010 at 5:02

Attachments: