You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@trafficserver.apache.org by zw...@apache.org on 2018/04/17 22:07:00 UTC

svn commit: r1829406 - /trafficserver/site/trunk/content/why-ats.mdtext

Author: zwoop
Date: Tue Apr 17 22:07:00 2018
New Revision: 1829406

URL: http://svn.apache.org/viewvc?rev=1829406&view=rev
Log:
Added more fluff

Modified:
    trafficserver/site/trunk/content/why-ats.mdtext

Modified: trafficserver/site/trunk/content/why-ats.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/trunk/content/why-ats.mdtext?rev=1829406&r1=1829405&r2=1829406&view=diff
==============================================================================
--- trafficserver/site/trunk/content/why-ats.mdtext (original)
+++ trafficserver/site/trunk/content/why-ats.mdtext Tue Apr 17 22:07:00 2018
@@ -32,7 +32,8 @@ Server may be particularity suited to yo
 # Fast # {#fast}
 
 ...it's fast! On cheap hardware we have measured up to *190k QPS for
-a 10k object*. In big setups it's only NIC bound.
+a 10k object*. In big setups it's only NIC bound, production use of up
+to 50Gbps has been meassured (on a single box).
 
 The reason why it can be so fast is Traffic Server's architecture: e.g.:
 make sure that in the critical path between the client's request and