|
December 06, 2009, 04:28 AM
|
|
I've tried to use the flash uploader from my browser and had a glitch this morning. I tried it again and finally uploaded 5 photos. Now I'm trying migratr and it is progressing at a very slow rate. This is also affecting my bandwidth to the nth degree. It's pretty awful. Is this a current glitch or problem with the site or are uploads normally this grotesquely sluggish?
|
| |
|
December 06, 2009, 12:15 PM
|
|
Well, whilst trying things out over the past couple of days, I've found uploads to be pleasantly speedy.
Your statements are contradictory. You claim that uploads progress at a very slow rate, yet that they are adversely impacting on your available bandwidth. If they're transferring unduly slowly, the whole problem is that they can't be making use of the bandwidth available and so are taking longer than necessary. If, however, they are using up all of your available bandwidth, then they are clearly going as fast as they can with your infrastructure. There isn't much that 23 can do to help you there.
Perhaps your network connection just isn't up to it...
|
| |
|
|
December 06, 2009, 01:16 PM
|
|
I would have to disagree. The Flickr uploader is hardly as sluggish as this migratr program. Even in the slowest moments of its history have I seen website load as badly as they did last night. My photo thumbnails on 23 were loading in bits and pieces...mostly pieces. Now that the uploading/exporting is done, the thumbnails and the site load properly. No, the exporting was very slow. It took all night. What I'd like to know is if there are other more efficient uploaders that can be used for 23. Maybe 23's network isn't up to it. How many server farms does 23 have to handle traffic?
|
| |
|
|
December 06, 2009, 01:46 PM
|
|
I just tried the online flash player uploader. I get a network or file error again at 3 percent done! Is there a known issue with uploading going on this weekend?
|
| |
|
|
December 06, 2009, 03:08 PM
|
|
I've just uploaded another photo with no problems whatsoever.
|
| |
|
December 06, 2009, 05:09 PM
|
|
RayPaul, let's see what the basic latency is, as this is the thing that caps theoretical throughput first:
From a command line (Terminal or cmd.exe, or a POSIX shell depending on your OS) run this:
ping www.23hq.com
Let it run for 5-10 rounds and hit control-C (if you have to.) For example, I get an average of 133 ms for a round-trip time. Which is not the fastest it has ever been, but my connection has to bounce over the Atlantic.
|
| |
|
|
December 06, 2009, 08:06 PM
|
|
I get 4 request timed out messages.
So the 23hq servers are in Europe only? I'm in the US.
If the site keeps rejecting the packets and my machine and the program I'm using has to keep sending the files my internet connection goes down to a crawl.
By point of comparison f I ping Flickr.com I get an average of 92 ms. For the www.nytimes.com site I get 131 ms on average.
Where are you located?
|
| |
|
Team 23
December 06, 2009, 08:16 PM
|
|
The servers are located in Copenhagen, Denmark -- but of course you shouldn't see packet losses our even timeouts during pings. In fact, our server provider guarantees a maximum of 110ms latency from North America.
So, can you mail me a traceroute from your location along with a dump of the ping -- then I'll make sure it's taken care of. The address is steffen@23company.com.
|
| |
|
December 06, 2009, 08:35 PM
|
|
Steffen, just in case this helps you, my pings from New Zealand to 23HQ.com are in the 325ms range.
|
| |
|
December 06, 2009, 09:11 PM
|
|
I see a typical 195 ms ping time, and the trace shows that the translatlantic hop is indeed under 100 ms.
10 pos-0-11-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.90.213) 10.352 ms 10.070 ms 23.578 ms
11 pos-0-9-0-0-cr01.denver.co.ibone.comcast.net (68.86.85.229) 37.986 ms 40.253 ms 50.068 ms
12 pos-0-11-0-0-cr01.chicago.il.ibone.comcast.net (68.86.86.185) 62.831 ms 63.413 ms 62.924 ms
13 pos-2-9-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.86.109) 98.893 ms 98.844 ms 97.646 ms
14 pos-0-1-0-0-pe01.111eighthave.ny.ibone.comcast.net (68.86.86.46) 98.779 ms 99.528 ms 101.958 ms
15 ge5-0-0-10g.nyk2nxg1.ip.tele.dk (195.215.109.69) 98.874 ms 98.809 ms 98.988 ms
16 te2-3.boanxc7.dk.ip.tdc.net (62.242.207.121) 195.241 ms 194.567 ms 195.027 ms
|
| |
|
|
December 06, 2009, 11:35 PM
|
|
Now all this information is well and good to know how some of us are getting uploads but I fail to understand why it is that the flickr desktop uploader or the juploader that I've used with flickr never had such all night uploading times other than the fact that your servers are in Denmark. I pinged 23 again tonight and there wasn't much packet losss and the requests did not time out this time. I got an average of 199 ms for the most recent ping.
|
| |
|
December 07, 2009, 12:33 AM
|
|
hey, i live in the US and have had no problems at all with uploading, via any method i have tried.
i've tried migratr, picturesync, email, pixelpipe and the web based uploader, and all have been extremely speedy - comparable to if not faster than flickr.
i will now add three question marks to this comment, for the sake of redundancy.
???
|
| |
