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

Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2018/10/22 21:54:26 UTC

[GitHub] rob05c commented on issue #2931: reuse single riak cluster connection, up riak heartbeat timeout

rob05c commented on issue #2931: reuse single riak cluster connection, up riak heartbeat timeout
URL: https://github.com/apache/trafficcontrol/pull/2931#issuecomment-431998231
 
 
   >with this patch only the first request is taking about 4-6 seconds, and subsequent requests are as fast as 72 ms.
   
   Excellent. Benchmarks FTW. And as I replied to John, I was mistaken about the health check. Though I am confused why it'd take ~5s to create the `Cluster` object, it seems like it should be trivial.
   
   >What if we run the DB query to check for new riak servers before every Riak request, but only reset the RiakCluster if the servers have actually changed from what's currently in use? I think that is possibly the best of both worlds.
   
   @rawlinp I agree, that sounds good to me

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services