Yeah, in talking w/ @raffi on the API team, I learned that simply by using the api.twitter.com URL when calling REST methods instead of the legacy format of using just twitter.com, you're using a separate and better hardware base. Hence, the chance for faster speeds. The twitter.com REST methods share the same hardware as the twitter.com website.
On Jan 15, 2:03 am, PJB <pjbmancun...@gmail.com> wrote: > Woo hoo... something must have changed... for at least the past 24 > hours, I am noticing incredible performance from API calls. Seems to > be at least 40% faster than earlier in the week.