help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Best practices RE: https api calls

‎10-22-2014 17:25

‎10-22-2014 17:25

Our servers currently make ~900k calls to your api each day.  Yesterday I deployed a code change to switch the protocol to https.  We don't have any errors, but I noticed our throughput fell significantly after the change.  Wireshark shows that we're recreating the SSL connection on each request, which creates significant overhead for your servers and ours.  I imagine this will be magnified in two weeks when you require all clients to use SSL.

 

Does your API support connection reuse?  Should we be using that?

Best Answer
Labels:
0 Votes
2 REPLIES 2

‎10-22-2014 17:29

‎10-22-2014 17:29

Yes we do. If you care about the performance, then absolutely you should make use of it. 

Best Answer
0 Votes

‎10-22-2014 17:34

In response to SunsetRunner

‎10-22-2014 17:34

Thanks for the quick reply!

 

I can have one of our developers make the change tomorrow.  Do you have example client code using the ruby oauth gem or Faraday?

 

Best Answer
0 Votes