how long does it take for a picture to download?

Canon EF 70-300mm f/4.5-5.6 DO IS USM

05/01/2006 07:26:49 PM · #1

We have broadband but it still takes on average 10-15 seconds for a picture to download.
How long does it take for you?
Does it affect how much you vote ? It sure does for me!

KarenNfld

05/01/2006 07:28:29 PM · #2

I have DSL, it is pretty well instant for a photo to appear.

cpanaioti

Canon EOS-40D

05/01/2006 07:30:08 PM · #3

I have broadband and it's pretty much instant.

Sigma 70-200mm f/2.8 EX DG APO IF for Pentax

05/01/2006 07:31:19 PM · #4

Just goes to show how behind broadband is here in NZ I hate to think how the dial-ups here manage!

Nobody

Pentax K-S2

05/01/2006 07:33:18 PM · #5

You probably have some local alternatives, but the following DSL Reports Speed Test will test your effective connection speed.

Dr.Confuser

Nikon D800

Nikon AF-S NIKKOR 24-70mm f/2.8G ED

05/01/2006 07:34:59 PM · #6

Broadband is used variously to refer to ISDN, DSL, Cable, T-1 and such. These function at different speeds and handle network congestion differently. What flavor of broadband do you have? Is the slow performance constant or do you have times when the performance is better?

05/01/2006 07:49:32 PM · #7

Sorry not sure of what flavour and its slow all the time. It's a bit of a controversy over here that broadband is so expensive and slow compared to other countries.
But I know it's an improvement from dial up :)

Nikon AF Nikkor 50mm f/1.8D

05/02/2006 02:26:07 AM · #8

Bump for the kiwis to comment

David.C

05/02/2006 02:29:04 AM · #9

Is it slow to download or to start downloading? That is, does part of the image show up, and then another part and so on, or does it all pretty much show up at once -- once it starts showing up at all.

David

crayon

Samsung Galaxy S24, S24+, S24 Ultra

05/02/2006 02:31:29 AM · #10

pretty instant...
say roughly 1-2 seconds.

GeneralE

Canon PowerShot S3 IS

Canon 12x IS USM (S3 IS built-in Lens) -- 36-432mm (35mm EQ)

05/02/2006 02:33:57 AM · #11

Originally posted by joynim:

Just goes to show how behind broadband is here in NZ I hate to think how the dial-ups here manage!

Well, to get from a server on the East Coast of the USA, the data has to pass through many different servers, halfway (or more) around the world. The miracle is that it only takes you 15 seconds to see the same image I'm looking at 10,000 miles away ...

There's software you can get (probably about $20-30 USD) which can trace the exact route (through which servers) the data has taken from the original source to you ... check at cnet.com

David.C

Nikon AF Nikkor 50mm f/1.8D

05/02/2006 02:47:01 AM · #12

Originally posted by GeneralE:

Originally posted by joynim:
Just goes to show how behind broadband is here in NZ I hate to think how the dial-ups here manage!

Well, to get from a server on the East Coast of the USA, the data has to pass through many different servers, halfway (or more) around the world. The miracle is that it only takes you 15 seconds to see the same image I'm looking at 10,000 miles away ...

There's software you can get (probably about $20-30 USD) which can trace the exact route (through which servers) the data has taken from the original source to you ... check at cnet.com

No need to pay for a basic trace. Just open a command prompt in Windows (or similar on other OS's) and type 'tracert' followed by the name of the server you want to trace your route to. For example, this is the route traced from my computer to DPC.

C:\> tracert //www.dpchallenge.com

Tracing route to //www.dpchallenge.com [198.77.14.211]
over a maximum of 30 hops:

. 1 ... 1 ms .. <1 ms .. <1 ms . 192.168.2.1
. 2 ... 9 ms .. 12 ms .. 11 ms . 10.10.241.1
. 3 .. 13 ms .. 20 ms .. 37 ms . 69.27.149.1
. 4 .. 13 ms .. 13 ms .. 18 ms . PIP-c3550.positech.net [69.27.136.1]
. 5 .. 17 ms .. 16 ms .. 25 ms . 69.27.135.60
. 6 .. 20 ms .. 29 ms .. 21 ms . Vinita-7200_Fa-0-0-105.k-powernet.com [69.27.135.69]
. 7 .. 55 ms .. 36 ms .. 44 ms . 67.98.6.185
. 8 .. 46 ms .. 39 ms .. 59 ms . P2-2.c0.gnwd.broadwing.net [216.140.14.65]
. 9 .. 59 ms .. 62 ms .. 73 ms . p3-0.c0.nwyk.broadwing.net [216.140.16.210]
10 .. 75 ms .. 61 ms .. 74 ms . 216.140.17.121
11 . 105 ms .. 66 ms .. 74 ms . p0-2-0.a1.wash.broadwing.net [216.140.8.90]
12 .. 65 ms .. 71 ms .. 65 ms . SprintNap.broadwing.net [216.140.9.10]
13 .. 73 ms .. 83 ms .. 72 ms . eqix.ge-0-0-0.gbr1.ash.nac.net [206.223.115.69]
14 .. 72 ms .. 91 ms .. 70 ms . 0.so-2-2-0.gbr2.nwr.nac.net [209.123.11.29]
15 .. 70 ms .. 80 ms .. 72 ms . 0.ge-2-3-0.gbr1.nyc.nac.net [209.123.11.173]
16 .. 91 ms .. 72 ms .. 79 ms . vlan96.esd1.nyc.nac.net [209.123.11.90]
17 .. 76 ms .. 81 ms .. 86 ms . pop1-nyc-fe-2-1.gtdn.net [207.99.73.90]
18 .. 95 ms .. 71 ms .. 85 ms . ge-0-1.aggr1.nyc1.sargasso.net [64.21.79.242]
19 .. 76 ms .. 92 ms .. 81 ms . //www.dpchallenge.com [198.77.14.211]

Trace complete.

19 hops and I barely notice the time before it's shown -- the first three just get me out of the local network to my ISP!

Different OS's most likely have something similar, but the exact name of the command may vary. IIRC it is 'traceroute' on Linux, but it's been a while since I've used that command on that OS.

David

/edit: dots added to help preserve formatting

Message edited by author 2006-05-02 02:52:55.

05/02/2006 02:57:32 AM · #13

Originally posted by David.C:

One part shows then another etc etc etc

05/02/2006 02:58:34 AM · #14

command prompt?

Nikon AF Nikkor 50mm f/1.8D

05/02/2006 03:20:38 AM · #15

Did it! With the help of my husband LOL!

C:\Documents and Settings\Charlie>tracert //www.dpchallenge.com

Tracing route to //www.dpchallenge.com [198.77.14.215]
over a maximum of 30 hops:

1 * * * Request timed out.
2 58 ms 61 ms 58 ms 222-152-208-1.jetstream.xtra.co.nz [222.152.208.
1]
3 141 ms 73 ms 73 ms 222.152.127.71
4 79 ms 69 ms 72 ms fid-int.tkbr4.global-gateway.net.nz [202.50.245.
198]
5 78 ms 70 ms 80 ms vlan-283.tkbr4.global-gateway.net.nz [202.50.245
.197]
6 75 ms 75 ms 71 ms pc1-30.tkbr3.global-gateway.net.nz [210.55.202.6
5]
7 203 ms 194 ms 201 ms 202.50.232.18
8 207 ms 193 ms 197 ms so2-0-0-0.labr4.global-gateway.net.nz [203.96.12
0.102]
9 197 ms 196 ms 197 ms sl-st20-la-6-2.sprintlink.net [144.232.154.209]

10 193 ms 196 ms 195 ms sl-bb21-ana-4-0.sprintlink.net [144.232.8.95]
11 201 ms 194 ms 194 ms sl-bb22-ana-15-0.sprintlink.net [144.232.1.174]

12 199 ms 203 ms 194 ms sprint-gw.la2ca.ip.att.net [192.205.32.185]
13 352 ms 351 ms 348 ms 12.123.222.38
14 372 ms 364 ms 367 ms tbr2-cl21.sl9mo.ip.att.net [12.122.10.13]
15 303 ms 303 ms 307 ms tbr2-cl7.cgcil.ip.att.net [12.122.10.45]
16 363 ms 345 ms 343 ms tbr1-cl22.cgcil.ip.att.net [12.122.9.133]
17 345 ms 342 ms 325 ms tbr1-cl14.n54ny.ip.att.net [12.122.10.1]
18 299 ms 302 ms 300 ms sar1-a300s3.n54ny.ip.att.net [12.123.0.153]
19 306 ms 297 ms 298 ms att-gige.esd1.nwr.nac.net [12.119.140.26]
20 297 ms 296 ms 291 ms 3.ge-3-0-0.gbr2.nwr.nac.net [209.123.11.189]
21 299 ms 298 ms 295 ms 0.ge-6-2-0.gbr2.nyc.nac.net [209.123.11.181]
22 345 ms 344 ms 344 ms vlan96.esd1.nyc.nac.net [209.123.11.90]
23 295 ms 297 ms 295 ms pop1-nyc-fe-2-1.gtdn.net [207.99.73.90]
24 308 ms 304 ms 298 ms ge-0-1.aggr1.nyc1.sargasso.net [64.21.79.242]
25 299 ms 301 ms 296 ms users.dpchallenge.com [198.77.14.215]

Trace complete.

So what does this tell me?

David.C

05/02/2006 04:18:52 AM · #16

Originally posted by joynim:

The first number is the number of hops it takes to reach that computer (or router or other such device). The first one sends the packet on to the 2nd and so on until it reaches the destination. The next three are the length of time it took to reach it. Three packets are sent so fluke times can be ignored, such as the first time on the 3rd hop that took twice as long as either of the other two. The last thing each line tells you is the name of the server (or it's internet address if it doesn't have a name).

Looking for large increases in time from one host to the next tells you were the delays are. In this trace the 7th hop take almost 3x as long as the previous hop did, and then there is another long delay between the 12th and 13th hops. Looking at the names of these hosts I see the first delay is just before it leaves NZ and another large delay just after getting to the US. It's like using public transportation, there is a wait to get on the bus and another when you get off again. Each packet has to wait to get onto the line that crosses the ocean, and then wait again when it gets to the other side before it can get out of it and on it's way again.

Sorry to say you will likely just have to live with it. There are some optimizations that can be made, but any ISP worth anything at all will have already made them (and most of them will only affect the first couple of hops in any event).

David

Message edited by author 2006-05-02 04:19:59.