Slow CP

dman

dman

Perch
Hello,

The CP is responding very slowly. I'm getting some response times between 270-550 ms. Is this normal??? Below are some tracert's for example:

Tracing route to xxxxx.com [64.187.103.71]
over a maximum of 30 hops:

1 9 ms 7 ms 7 ms xx.xx.xx.xx
2 8 ms 7 ms 7 ms GIG2-1.HNBHCA1-RTR2.socal.rr.com [xx.xx.xx.xx]

3 9 ms 10 ms 7 ms SRP1-0.GDGVCA1-GSR1.socal.rr.com [24.30.161.129]

4 11 ms 11 ms 11 ms SO-1-1-0.LSANCA1-RTR1.socal.rr.com [66.75.161.17
4]
5 11 ms 15 ms 10 ms pop1-las-P5-0.atdn.net [66.185.143.5]
6 11 ms 13 ms 12 ms bb2-las-P0-0.atdn.net [66.185.137.130]
7 12 ms 11 ms 12 ms pop2-las-P1-0.atdn.net [66.185.137.163]
8 11 ms 11 ms 12 ms GlobalCrossing.atdn.net [66.185.148.50]
9 124 ms 227 ms 237 ms te1-1-10G.ar1.MIA2.gblx.net [67.17.108.62]
10 73 ms 71 ms 73 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net
[64.212.16.166]
11 277 ms 141 ms 271 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]

12 72 ms 72 ms 71 ms webhosting-9.border5.mia003.pnap.net [216.52.162
.66]
13 71 ms 71 ms 72 ms rtr1.m****here.biz [204.10.104.77]
14 71 ms 73 ms 71 ms 64.187.103.71

Trace complete.

tracert xxxxx.com

Tracing route to xxxxx.com [64.187.103.71]
over a maximum of 30 hops:

1 7 ms 8 ms 7 ms xx.xx.xx.xx
2 7 ms 7 ms 11 ms GIG2-1.HNBHCA1-RTR2.socal.rr.com [xx.xx.xx.xx]

3 7 ms 8 ms * SRP1-0.GDGVCA1-GSR1.socal.rr.com [24.30.161.129]

4 9 ms 11 ms 9 ms SO-1-1-0.LSANCA1-RTR1.socal.rr.com [66.75.161.17
4]
5 11 ms 9 ms 9 ms pop1-las-P5-1.atdn.net [66.185.133.193]
6 11 ms 12 ms 11 ms bb2-las-P0-0.atdn.net [66.185.137.130]
7 11 ms 12 ms 10 ms pop2-las-P1-0.atdn.net [66.185.137.163]
8 10 ms 11 ms 10 ms GlobalCrossing.atdn.net [66.185.148.50]
9 86 ms 87 ms 87 ms te1-1-10G.ar1.MIA2.gblx.net [67.17.108.62]
10 73 ms 71 ms 71 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net
[64.212.16.166]
11 72 ms 72 ms 71 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]

12 220 ms 73 ms 71 ms webhosting-9.border5.mia003.pnap.net [216.52.162
.66]
13 72 ms 72 ms 72 ms rtr1.m****here.biz [204.10.104.77]
14 77 ms 70 ms 71 ms 64.187.103.71

Trace complete.

tracert xxxxx.com

Tracing route to xxxxx.com [64.187.103.71]
over a maximum of 30 hops:

1 7 ms 7 ms 7 ms xx.xx.xx.xx
2 7 ms 7 ms 11 ms GIG2-1.HNBHCA1-RTR2.socal.rr.com [xx.xx.xx.xx]

3 9 ms 9 ms 7 ms SRP1-0.GDGVCA1-GSR1.socal.rr.com [24.30.161.129]

4 12 ms 11 ms 11 ms SO-1-1-0.LSANCA1-RTR1.socal.rr.com [66.75.161.17
4]
5 11 ms 11 ms 11 ms pop1-las-P5-1.atdn.net [66.185.133.193]
6 10 ms 11 ms 11 ms bb2-las-P0-0.atdn.net [66.185.137.130]
7 12 ms 11 ms 10 ms pop2-las-P1-0.atdn.net [66.185.137.163]
8 11 ms 10 ms 10 ms GlobalCrossing.atdn.net [66.185.148.50]
9 85 ms 87 ms 87 ms te1-1-10G.ar1.MIA2.gblx.net [67.17.108.62]
10 70 ms 71 ms 71 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net
[64.212.16.166]
11 72 ms 71 ms 70 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]

12 71 ms 71 ms 71 ms webhosting-9.border5.mia003.pnap.net [216.52.162
.66]
13 72 ms 72 ms 72 ms rtr1.m****here.biz [204.10.104.77]
14 71 ms 69 ms 70 ms 64.187.103.71

Trace complete.

tracert xxxxx.com

Tracing route to xxxxx.com [64.187.103.71]
over a maximum of 30 hops:

1 10 ms 7 ms 7 ms xx.xx.xx.xx
2 8 ms 7 ms 9 ms GIG2-1.HNBHCA1-RTR2.socal.rr.com [xx.xx.xx.xx]

3 8 ms 9 ms 9 ms SRP1-0.GDGVCA1-GSR1.socal.rr.com [24.30.161.129]

4 11 ms 12 ms 12 ms SO-1-1-0.LSANCA1-RTR1.socal.rr.com [66.75.161.17
4]
5 11 ms 11 ms 11 ms pop1-las-P5-1.atdn.net [66.185.133.193]
6 12 ms 10 ms 11 ms bb2-las-P0-0.atdn.net [66.185.137.130]
7 10 ms 11 ms 17 ms pop2-las-P1-0.atdn.net [66.185.137.163]
8 553 ms 91 ms 12 ms GlobalCrossing.atdn.net [66.185.148.50]
9 86 ms 87 ms 87 ms te1-1-10G.ar1.MIA2.gblx.net [67.17.108.62]
10 72 ms 76 ms 72 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net
[64.212.16.166]
11 71 ms 71 ms 71 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]

12 70 ms 71 ms 71 ms webhosting-9.border5.mia003.pnap.net [216.52.162
.66]
13 72 ms 71 ms 71 ms rtr1.m****here.biz [204.10.104.77]
14 70 ms 71 ms 72 ms 64.187.103.71

Trace complete.

tracert xxxxx.com

Tracing route to xxxxx.com [64.187.103.71]
over a maximum of 30 hops:

1 8 ms 7 ms 7 ms xx.xx.xx.xx
2 7 ms 7 ms 7 ms GIG2-1.HNBHCA1-RTR2.socal.rr.com [xx.xx.xx.xx]

3 9 ms 9 ms 7 ms SRP1-0.GDGVCA1-GSR1.socal.rr.com [24.30.161.129]

4 11 ms 11 ms 11 ms SO-1-1-0.LSANCA1-RTR1.socal.rr.com [66.75.161.17
4]
5 10 ms 16 ms 12 ms pop1-las-P5-1.atdn.net [66.185.133.193]
6 17 ms 10 ms 12 ms bb2-las-P0-0.atdn.net [66.185.137.130]
7 11 ms 12 ms 11 ms pop2-las-P1-0.atdn.net [66.185.137.163]
8 11 ms 11 ms 10 ms GlobalCrossing.atdn.net [66.185.148.50]
9 85 ms 85 ms 87 ms te1-1-10G.ar1.MIA2.gblx.net [67.17.108.62]
10 71 ms 71 ms 70 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net
[64.212.16.166]
11 71 ms 72 ms 71 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]

12 322 ms 277 ms 278 ms webhosting-9.border5.mia003.pnap.net [216.52.162
.66]
13 71 ms 72 ms 70 ms rtr1.m****here.biz [204.10.104.77]
14 71 ms 74 ms 70 ms 64.187.103.71

Trace complete.
 
tracerts are fine, it is just the hours between midnight and 4-5am that cron jobs are running that it can be slow, and sometimes it will get stuck processing an account.
 
Hey Stephen. This makes sense at night and I was working in their in the wee hours of the morning. It does seem to be a little better today but still a little lag time. I'll keep working with it and see if it improves. I wish the Live Chat support rep. would have told me this last night. He kept saying it was my browser or system cache. But your explanation makes much more sense. He said there was no issue as well. Maybe tell the support reps to say this instead. Thanks!
 
Well they may not see much difference to be honest, they are on a shared connection that sees some lag sometimes, but at night it is very visible from a DSL line on a non shared connection :)
 
You must log in or register to reply here.
Back
Top