Slow loading of jowett.net

[Keith Andrews]

Over the last week or so the jowett.net servers/data bases have been very slow to respond to pages
Jowett.net in partular forums and gallery, which can take several minutes and occassionaly time out.
This is the only web site we have issues with and from 4 different computers.
Usually when the pages do load, things like picuturs , graphics are not there....
ie the only graphis loaded on this page are the logo to left and 3 smilies on the right.

[Keith Clements]

OK. I will look into it.

[Forumadmin]

I have put a monitor on the server and asked the hosting company. Server status is saying it is OK. Please advise specific times any degradation is noticed or when it is OK.

[Keith Andrews]

Just got this when page doesnt load .....then refeshed
Note the lack of graphics

[Keith Andrews]

Now if u look at the clock time on the task bar 12:15 and the time of the post...11:10
Note 1 hr out due to day ligh savings the page is still loading 5 mins later

[Forumadmin]

Over the last week I have been conversing with the hosting company trying to pin down the problem on jowett.net (not jowett.org). KA reported the problem and both he and I have been using the tracert command to prove a problem exists.

So has anybody else had a problem getting to jowett.net or with response from jowett forum or gallery? Note we must distinguish between the three areas. Jowett Talk and Gallery use a database whereas jowett.net is just a static website. A static website should respond within a few milliseconds and perhaps take a couple more seconds to deliver all the text and pictures. A page constructed from a database will be slower but should respond within two seconds and deliver the whole page within 10 seconds.

If you are having a slow response please take a note of the time of day and, using a stop watch, how long response and complete page load takes. If you can, please use the command tracert as follows.

Perform a traceroute on Windows
1. Click on start.
2. Click in the search box.
3. Then type cmd (you may need to type command in Windows 95/98/ME).
4. Once you have your Terminal box open, just type "tracert jowett.net >test1" without the quotes!
5. Please then attach in an email or post the contents of test1 on JowettTalk in this topic. You can open "test1" with notepad and have a look.

[PJGD]

I am not having slow loading issues here in Michigan.
This is what I get:
traceroute to jowett.net (69.175.15.178), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 1.664 ms 1.290 ms 0.611 ms
2 192.168.1.1 (192.168.1.1) 1.294 ms 1.079 ms 0.940 ms
3 192.168.251.1 (192.168.251.1) 7.510 ms 4.696 ms 4.997 ms
4 71.238.74.1 (71.238.74.1) 45.403 ms 29.695 ms 49.847 ms
5 te-8-2-ur02.rochestrhlls.mi.michigan.comcast.net (68.85.85.129) 14.755 ms 14.052 ms 14.639 ms
6 te-8-1-ur02.clinton2.mi.michigan.comcast.net (68.87.191.21) 19.219 ms 18.377 ms 15.272 ms
7 te-0-7-0-1-ar01.taylor.mi.michigan.comcast.net (68.87.190.221) 25.309 ms 23.895 ms 25.094 ms
8 pos-3-2-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.90.177) 35.217 ms 34.153 ms 35.047 ms
9 pos-0-12-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.85.30) 40.346 ms 39.886 ms 44.670 ms
10 pos-0-4-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.88.146) 45.324 ms 49.484 ms 45.371 ms
11 be-12-pe03.350ecermak.il.ibone.comcast.net (68.86.84.190) 44.961 ms 38.958 ms 45.331 ms
12 173-167-57-126-static.hfc.comcastbusiness.net (173.167.57.126) 45.445 ms 43.710 ms 51.102 ms
13 ae1-40g.cr2.ord1.us.nlayer.net (69.31.111.137) 44.297 ms 44.721 ms 41.664 ms
14 ae2-20g.ar1.ord6.us.nlayer.net (69.31.110.254) 45.201 ms
ae1-20g.ar1.ord6.us.nlayer.net (69.31.110.250) 49.462 ms 50.240 ms
15 as32475.ae6.ar1.ord6.us.nlayer.net (69.31.110.202) 45.111 ms
as32475.ae7.ar1.ord6.us.nlayer.net (69.31.111.30) 44.823 ms
as32475.ae6.ar1.ord6.us.nlayer.net (69.31.110.202) 44.861 ms
16 asw-fr181.ord03.singlehop.net (173.236.0.162) 44.528 ms
asw-fr181.ord03.singlehop.net (173.236.0.166) 55.968 ms
asw-fr181.ord03.singlehop.net (173.236.0.162) 47.201 ms

Philip

[Keith Clements]

jowett.net was down for about 6 hours yesterday, apparently the server was doing a file system check. I was in discussion with hosting support during that time.

Sorry for this.

I am now in discussions with billing department!

[Keith Andrews]

The site is consistantty quick now

[Keith Clements]

Let us hope it stays that way. I think the system must have had a bad disk. Perhaps rebuilding it cleared out the c**p.

[Keith Andrews]

Nar m8..typical IT ppl get paid heaps, and full of BS and just dont bother to do routine mainance check server logs etc
Then when things get bad and ppl complain it.."OH gee I havnt done any maintance for a few months, gee I cant tell anyone that..OH well I will just blame it on a connection and while they are doing that I will compact a few data bases , defrag the drives and do an 'oil change'... they are too stupid to know the difference"

I work with these idiots..the more bloody quailfied they are the worse they are....the good old school experiance guys are now retiring