epriestley 5f26dd9b66 Use futures to improve clustered repository main page performance ... Summary: Ref T11954. In cluster configurations, we get repository information by making HTTP calls over Conduit. These are slower than local calls, so clustering imposes a performance penalty. However, we can use futures and parallelize them so that clustering actually improves overall performance. When not running in clustered mode, this just makes us run stuff inline. Test Plan: - Browsed Git, Mercurial and Subversion repositories. - Locally, saw a 700ms wall time page drop to 200ms. Reviewers: chad Reviewed By: chad Maniphest Tasks: T11954 Differential Revision: https://secure.phabricator.com/D17009		2016-12-08 07:26:32 -08:00
..
application	Move FontIcon calls to Icon	2016-01-28 08:48:45 -08:00
call	Conduit accept int/bool parameters as strings	2016-10-14 14:45:57 +00:00
controller	Conduit accept int/bool parameters as strings	2016-10-14 14:45:57 +00:00
garbagecollector	Remove all references to the Conduit ConnectionLog	2015-12-14 15:25:11 -08:00
interface	Formalize custom Conduit fields on objects	2015-12-14 11:54:13 -08:00
method	Use PhabricatorCachedClassMapQuery in Conduit method lookups	2016-12-06 08:38:46 -08:00
parametertype	Fixed undefined variable error in call from ConduitIntListParameterType	2016-10-17 12:38:15 +00:00
protocol	Conduit accept int/bool parameters as strings	2016-10-14 14:45:57 +00:00
query	Slightly modernize ConduitTokenQuery	2016-12-06 08:45:43 -08:00
settings	Allow administrators to configure global default settings	2016-06-05 13:15:06 -07:00
ssh	phtize all the things	2015-05-22 21:16:39 +10:00
storage	Use futures to improve clustered repository main page performance	2016-12-08 07:26:32 -08:00