Loading Profile...
Frequent timeouts when "checking for bandwidths"
Hi,
I've been having a lot of timeouts when "checking for bandwidth limits" over the last few months. I have a lot of pictures (close to 20k) and sets (several hundreds). It looks like it ends up working if I try several times in a row, which may mean that FlickrExport just needs to hit the same Flickr frontend twice and benefit from a cache at some level. According to tcpdump, it happens during flickr.people.getUploadStatus. Tcpdumps of typical failing and succeeding exchanges available upon request (just let me know if I need to obfuscate more than just the keys).
I was wondering if there's a way to tweak FlickrExport's timeout for my own needs or, since I have a Pro account with unlimited bandwidth, if I can just disable the bandwidth limit check?
Thanks.
I've been having a lot of timeouts when "checking for bandwidth limits" over the last few months. I have a lot of pictures (close to 20k) and sets (several hundreds). It looks like it ends up working if I try several times in a row, which may mean that FlickrExport just needs to hit the same Flickr frontend twice and benefit from a cache at some level. According to tcpdump, it happens during flickr.people.getUploadStatus. Tcpdumps of typical failing and succeeding exchanges available upon request (just let me know if I need to obfuscate more than just the keys).
I was wondering if there's a way to tweak FlickrExport's timeout for my own needs or, since I have a Pro account with unlimited bandwidth, if I can just disable the bandwidth limit check?
Thanks.
I’m a sad panda
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
-
Inappropriate?Hi Olivier,
tcpdumps would be useful, but please send them to info-at-connectedflow.com, as such files can sometimes be hard to read on the web.
I'm hoping that I can rework the login process a bit for FlickrExport 3.5, the release that's due to drop Tiger support. There are some nicer Leopard-era APIs that might help this a bit.
In most cases, and getUploadStatus is one, FlickrExport uses the default timeout of 60 seconds. Do you have a sense of how long the timeout would need to be for you to get a solid connection? -
Inappropriate?Thanks Fraser.
tcpdumps sent. I'm not sure what a good timeout would be. By any chance, would you have a script or program that's already written to try out several values? I can probably write something quick and dirty if you don't but, just in case... -
Inappropriate?Alright, I have a script ready. I'll gather some statistics and let you know. Looking at the Flickr API, though, I was wondering if it would be possible for you to first call flickr.people.getInfo, see if ispro is 1 -- in which case there's no bandwidth limit -- and then call flickr.people.getUploadStatus only if it's relevant to know the limit?
Not sure it would be faster (I'll hopefully figure out soon)... Just a thought. -
Inappropriate?Having a look at my early numbers, a 120-second timeout would be a significant improvement but the safest value is more likely to be around 160 seconds. flickr.people.getInfo always returns within 5 seconds, though, so calling flickr.people.getUploadStatus only for non-pro accounts would be a definite win for all big users in my opinion.
-
Inappropriate?Thanks for the information, Olivier. I've raised a question in the Flickr API group, with a link here, to see if I can find out why the call is taking so long for you. Can you reply to this thread with a link to your Flickr stream?
Thanks,
Fraser -
Inappropriate?id: 7495159@N07
alias: ob-v
Note that most of my pictures are not public. -
Inappropriate?As an illustration, here are some graphs over 18 hours of the time it takes to do getUploadStatus and getInfo on my account. Probing interval was 15 minutes. It looks like I can keep getUploadStatus' time below 120 seconds if I probe every 5 minutes, which is interesting (and means that a workaround for me would be to have a cron keeping Flickr cache warm).
EMPLOYEE
