This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "snap-website".
The branch, master has been updated
via 5c3d451854354e7383cd3242594d97a42594367c (commit)
from 0f269203a6af44a478d6fcea5f028abf7334027b (commit)
Summary of changes:
templates/benchmarks.md | 106 ----------------------------------------------
templates/benchmarks.tpl | 15 +++----
2 files changed, 7 insertions(+), 114 deletions(-)
delete mode 100644 templates/benchmarks.md
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 5c3d451854354e7383cd3242594d97a42594367c
Author: Mighty Byte <[email protected]>
Date: Mon Nov 22 09:32:49 2010 -0500
Made /benchmarks point to the most recent benchmark blog post.
diff --git a/templates/benchmarks.md b/templates/benchmarks.md
deleted file mode 100644
index 9c64dcf..0000000
--- a/templates/benchmarks.md
+++ /dev/null
@@ -1,106 +0,0 @@
-Web Framework Benchmark Description
-===================================
-
-To compare the performance of Snap to that of other web servers/frameworks, we
-ran some simple benchmarks using httperf: pong and file. In the pong
-benchmark, servers sent a 4-byte response of "PONG". The file benchmark sent a
-50KB PNG image file as its response. Our results and nodes are described
-below.
-
-Most of the benchmarks were run with the following httperf command line
-options:
-
-~~~~~~~~~~~~~~~~~~
-httperf --hog --num-conns 1000 --num-calls 1000 --burst-length 20 --port 3000
--rate 1000 --uri=/pong
-~~~~~~~~~~~~~~~~~~
-
-All benchmarks were run on a dual quad-core Xeon E5345 2.33 GHz workstation
-with 8 gigs of RAM. In all these tests, we compiled Snap with "-threaded" and
-ran it with "+RTS -A4M -N4 -qg0 -qb -g1". Using more than four threads caused
-the performance to decrease. This is certainly a good area for future
-improvement in Snap.
-
-Disclaimer: We are not experts at optimizing these web frameworks. It
-is almost certain that the results for other frameworks are unfairly
-low. If you're interested in the details, the code we used is in a
-[github repository](http://github.com/snapframework/snap-benchmarks).
-We're always willing to update our benchmarks with optimizations that
-don't take an inordinate amount of effort to set up.
-
-### Pong Benchmark
-
-The pong benchmark is quite simple, but there was a large amount of variation
-in performance. Here is a chart of responses per second (higher numbers
-are better):
-
-
-
-#### The Numbers
-
-<table>
- <tr>
- <td>RoR</td>
- <td>Grails</td>
- <td>Happstack</td>
- <td>Apache+PHP</td>
- <td>Snap</td>
- </tr>
- <tr>
- <td>258</td>
- <td>796</td>
- <td>8578</td>
- <td>8843</td>
- <td>23997</td>
- </tr>
-</table>
-<br />
-
-It should be noted that the Happstack benchmark is not multithreaded. We
-compiled Happstack with -threaded and when run with "+RTS -N4", the test never
-finished. When we aborted httperf, it reported a rate of 12.6
-requests/second. We also tried running it with with the same "+RTS -A4M -N4
--qg0 -qb -g1" runtime options that we used with Snap. This caused a stack
-overflow.
-
-### File Benchmark
-
-The file benchmark tests the ability to serve static content from disk. The
-results here were a little closer together than the pong results, but we still
-see the same general pattern.
-
-
-
-#### The Numbers
-
-<table>
- <tr>
- <td>RoR</td>
- <td>Grails</td>
- <td>Happstack</td>
- <td>Apache</td>
- <td>Snap</td>
- </tr>
- <tr>
- <td>360</td>
- <td>1769</td>
- <td>2455</td>
- <td>4126</td>
- <td>7206</td>
- </tr>
-</table>
-<br />
-
-In this test, we had more problems because Happstack does not support
-pipelining. So we switched to the following httperf line for Happstack:
-
-~~~~~~~~~~~~~~~~~~
-httperf --hog --num-conns 100000 --num-calls 1 --burst-length 1 --port 8080
--rate 10000 --uri=/FiringGeometry.png
-~~~~~~~~~~~~~~~~~~
-
-This means that Happstack's results in this test are not really an
-apples-to-apples comparison with the other frameworks, but they're still
-somewhat meaningful since they reflect a deficiency in the server.
-
-See the [raw test output](/bench-raw-results.txt) for more detailed
-httperf output.
-
diff --git a/templates/benchmarks.tpl b/templates/benchmarks.tpl
index 76c2ce8..488f08c 100644
--- a/templates/benchmarks.tpl
+++ b/templates/benchmarks.tpl
@@ -1,9 +1,8 @@
-<static>
- <bind tag="subtitle">: Benchmarks</bind>
- <apply template="page">
- <div class="singlecolumn">
- <markdown file="benchmarks.md"/>
- </div>
- </apply>
-</static>
+<html>
+<head>
+<meta http-equiv="REFRESH"
content="0;url=/blog/2010/11/17/snap-0.3-benchmarks"/>
+</head>
+<body>
+</body>
+</html>
-----------------------------------------------------------------------
hooks/post-receive
--
snap-website
_______________________________________________
Snap mailing list
[email protected]
http://mailman-mail5.webfaction.com/listinfo/snap
