OS2 World.Com Forum
2012.05.21, 23:31:43 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Troubleshooting a web performance problem, where to go?  (Read 8510 times)
Dave Palmer
Jr. Member
**
Posts: 72


View Profile
« on: 2009.01.23, 23:21:42 »

Strange performance problem has just started.

3 websites which I maintain are now difficult and very slow to access with my Warp system.  I have long delays using Firefox, and FTP clients (FireFTP, etc.) have difficulty signing in.

I've not made any software changes. 

I have a companion machine, running xp, through the same ethernet converter, thru the same dsl modem and it performs normally.

I can and did swap (removable drives) OS/2 with another XP drive, and using the same exact hardware system  as OS/2 , XP accesses things  normally.

Back on my OS/2 system, all other web sites perform normally.  No performance problems.

What would be a reasonable approach to solving this?  I am stymied. 

the three sites are theblackriver.net, oakvilleschools.org, fotloakville.org

Thanks,
Dave
Logged
warpcafe
Global Moderator
Hero Member
*****
Posts: 746


Failure is not an option.


View Profile
« Reply #1 on: 2009.01.24, 12:10:24 »

Hi Dave,

that's a tough one from the description. I went thru it 3 or 4 times and each time ended up with "that can't be the cause, since [site|machine] works in another constellation". Phew.

So let's rule out:
- it can't be the webservers as any other OS has no problem acessing it
- it can't be the OS/2-based browser since "all other" websites are working OK
- it can't be the client machines hardware since swapping it provides the same results
- it can't be the network since all client machines use the same one

Really, this leaves me puzzled. But OTOH what that boils down to is:
It must be a problem between exactly the os/2-based client and the websites in question. Starting by this approach, there are two questions that come to mind now:
- Is there any kind of javascript or flash being used in these webpages?
  (perhaps also by somekind of banner or ad stuff, (i)frame, being loaded from 3rd party servers)
- Did you try clearing the cache of your browser (and/or the server if that is using some flavor of CMS...)?

From your description I seem to understand that the webserver are not run "locally" meaning in your LAN, but somewhere that you need to connect to by DSL/Cable broadband, right? (If not, there might still be some kind of DNS or network problem...)

Regards, HTH
Thomas
Logged

"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy
warpcafe
Global Moderator
Hero Member
*****
Posts: 746


Failure is not an option.


View Profile
« Reply #2 on: 2009.01.24, 18:58:31 »

Hi, it's me again...

sorry but looking at your post again, it seems I missed out on 3 letters from it: "FTP"
If FTP connections are also suffering form the symptom mentioned, then obviously anything "embedded" on a website doesn't matter. Now it really looks like some kind of networking problem.
If its name resolution... have you (or "something") made any modifications to e.g. the "hosts" file on the machine? Or within the TCP/IP setup? Perhaps also a look into the servers logfiles can give a clue.

Sorry for the mess I left you with. Wink
HTH
Thomas
Logged

"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy
RobertM
Global Moderator
Hero Member
*****
Posts: 2011



View Profile WWW
« Reply #3 on: 2009.01.24, 21:10:26 »

Hi,

Are you trying to connect to the daemons via domain name or IP? I ran into a similar problem last week (except reversed) where the Windows machine on our network was having problems, but the OS/2 machines were not. Turned out to be a DNS issue (our host seems to have either been having trouble with a DNS server or replaced it with one on another IP). Changing the DNS info on the Windows machine resolved the problem, which was affecting, oddly, only certain locations (for of course, any service).
Logged

|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|

Dave Palmer
Jr. Member
**
Posts: 72


View Profile
« Reply #4 on: 2009.01.24, 21:20:23 »

Thanks guys for the tips and info.

I stay as perplexed as ever, but starting this morning (Saturday) everything works fine.

I wrote the ISP and received an answer which I did not act upon because everything is now working.

Before things were 'fixed' I had already cleared the cache, several times, and all the accesses were by domain names.

It's frustrating when bugs go away - 'cause I know they will return - at the worst possible moment.

Thanks again,
Dave
Logged
warpcafe
Global Moderator
Hero Member
*****
Posts: 746


Failure is not an option.


View Profile
« Reply #5 on: 2009.01.25, 13:01:32 »

Hi Dave,

glad it worked out for you. If you say all "adressing" is done by host names, then this matches with what I was feeling it to be the possible cause (DNS...) and also what RobertM appears to be suspecting. Perhaps your ISP/hosting comp.  did some (mis-) configuration changes? No idea however how that might struck OS/2 clients only. Wink

Cheers,
Thomas
Logged

"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy
RobertM
Global Moderator
Hero Member
*****
Posts: 2011



View Profile WWW
« Reply #6 on: 2009.01.25, 21:01:45 »

Hmmm... a bunch of the big nameservers were being DDOSd the last few days... wonder if that was related...
Logged

|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.14 | SMF © 2006-2011, Simple Machines LLC
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!