3 ms·
The increased latency is caused by API calls that the app has to make to Sedo for new queries. I've spent a lot of time optimizing it lately, but agree that the
by matt1 14y ago
The increased latency is caused by API calls that the app has to make to Sedo for new queries. I've spent a lot of time optimizing it lately, but agree that there's still room for improvement. It comes down to a tradeoff: would you rather get more premium results but have to wait a little while longer or get less results but have them quickly? For now I've taken the middle road, but that may change depending on how it affects usage.
Appreciate you bringing it up though and for suggesting alternatives.
- eli 14y agoPerhaps you could load fewer premium results beforehand but load the rest via AJAX?
- matt1 14y agoIt's actually all done via Ajax that way it doesn't affect the page load time. The search itself is also done on a separate server that way it doesn't tie up any of the app's dynos on Heroku (go go JSONP). I could make an initial API call and get a handful of results, but handling the remainder would be tricky. For example, let's say that the preliminary search returns 12 domains and I immediately display them to the user. Ten seconds later the second Ajax call returns an additional 60 premium domains. How do I display those to folks in a non-intrusive way? I'm open to suggestions :)