aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Phillips <david@sighup.nz>2017-02-17 15:16:13 +1300
committerDavid Phillips <david@sighup.nz>2017-02-17 15:16:13 +1300
commitea11f0c71f1617bbfdb5a5ef6644e34cb0192e29 (patch)
tree4f3b5dc181fa6215f30d0f84070b8107dbe20741
parent459bdbc70eb243f88f21cf1da23e5d811c0f0a00 (diff)
downloadfractal-gen-opencl-ea11f0c71f1617bbfdb5a5ef6644e34cb0192e29.tar.xz
Add more performance data to README
-rw-r--r--README.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/README.md b/README.md
index 1b54b7b..7fcd92d 100644
--- a/README.md
+++ b/README.md
@@ -25,4 +25,8 @@ For example, using the CPU-based fractal-gen, a 10240x10240 pixel image at
1000 iteration cutout per pixel, the image will complete in just under 4
minutes when running on all 32 threads of a dual-Xeon E5-2670 setup. Compare
this to the runtime of this software on a (much cheaper) NVIDIA GTX 1070; about
-0.5 to 1 second. The gap only widens with more detail.
+0.5 to 1 second.
+
+The gap only widens with more detail. Keeping the same image dimensions and
+climbing up to 10000 iterations, the Xeons will take 2200 seconds; just under
+37 minutes. The GTX 1070 takes just over 1 second.