Add new WebSocket benchmark graph

2018-10-30 07:06:30 +01:00
parent 57255c874d
commit 16bd859b0c
4 changed files with 8 additions and 2 deletions
@@ -55,4 +55,8 @@ A free & open source ([Zlib](LICENSE)) project since 2016. Kindly sponsored by [
 Commercial support is available via a per-hourly consulting plan or as otherwise negotiated. If you're stuck, worried about design or just in need of help don't hesitate throwing [me, the author](https://github.com/alexhultman) a mail and we'll figure out what's best for both parties. I want your business to have a proper understanding of the problem before rushing in to one of the many pitfalls.

 #### Excel across the board.
-![](misc/bigshot_lineup.png)
+All that glitters is not gold. Especially so in a market driven by flashy logos, hype and pointless badges.
+
+Http | WebSockets
+--- | ---
+![](misc/bigshot_lineup.png) | ![](misc/websocket_lineup.png)
@@ -6,7 +6,9 @@ The world needs more like you. I could talk about how stupid and gullible 95% of
 * Never accept random *numbers* which has no *point of reference* to similar software projects. The number "1 million" might sound fancy but without *any* kind of reference to *other* projects there's no knowing the worth of such a number. Comparative benchmarks are the only ones worth taking in. Think for yourself - how can the author claim "fast" if he/she has no benchmarks of what *others* are doing?
 * Most people who do benchmarks are complete monrons and do not know their ass from their head. Always make sure to *normalize* performance by spent CPU-time. That is, do NOT compare performance of software demanding 100% CPU-time on 57 CPU cores, with software running on 5% CPU-time on 1 CPU core. You would be stunned if you knew how few people actually care to even check this before posting their results to their literally millions of gullible followers.

-![](../misc/bigshot_lineup.png)
+Http | WebSockets
+--- | ---
+![](../misc/bigshot_lineup.png) | ![](../misc/websocket_lineup.png)

 ### The bystander effect (todo: shorten this)
 Having many users and many "stars" does not constitute a confirmation of any such *claims*. In fact, the opposite is more often true than not. How can this be true? Well for starters, actual performance often come with restrictions and more cumbersome APIs and it turns out most people are not really interested in doing more work than what they absolutely have to. Programmers want to *believe* their overly abstract garbage collected functional one liners to be "more efficient than machine code". They want to have the cake, and a cake cloning device too.