Server gurus - A question - DPChallenge Forums

06/22/2006 11:11:32 AM · #1

I have a server running at home using apache.

When i connect to the server with another computer at home it all works fine but the connecting isn't very fast.

If i look at the files on the server in windows explorer(photos for example) through a network connection they load fast and find.

If I load a web page with the full sized photos on them they load VERY slowly.

It seems the connection between the two computers is good enough as the files load quickly through windows explorer, but when they have to go through a website why do they load so turtle slow ??? is there a setting in apache I need to change for max speed or something?

thanks

06/22/2006 11:16:02 AM · #2

I'm not sure about settings, but LAN transfer is going to be MUCH faster than internet transfer. So this might just be normal.

06/22/2006 11:20:00 AM · #3

Originally posted by SamDoe1:

I'm not sure about settings, but LAN transfer is going to be MUCH faster than internet transfer. So this might just be normal.

I agree but that is the problem, because when connecting to the server at home through a browser I am still within my LAN. The home server isn't even connected to the internet.

06/22/2006 11:22:32 AM · #4

Originally posted by leaf:

I agree but that is the problem, because when connecting to the server at home through a browser I am still within my LAN. The home server isn't even connected to the internet.

No idea then, what web browser are you using?

Message edited by author 2006-06-22 11:22:45.

06/22/2006 11:42:07 AM · #5

firefox

06/22/2006 11:51:57 AM · #6

Try using IE, might work better.

06/22/2006 11:59:26 AM · #7

well I was doubtful.. I gave it a try, .. same speed. SLOW :(

06/22/2006 12:00:48 PM · #8

I have a little feeling that inside the server there is a setting stoping connections from going to fast so that if it were connected to the internet one person couldn't hog all the band width. However i WANT that. I want to be able to hog 100% of the bandwith instead of getting the measly dribble.

DjFenzl

06/22/2006 12:00:52 PM · #9

If you mean you are connecting through the internet to your Apache server and it's going slow - that is the problem.

Most broadband ISP's severely limit your upload speeds - -0usually to 128kb.

A word of warning too, in virtually all ISP TOS you are not allowed to connect a server to the internet theough their connection. Doing so will violate the TOS at which point they may disconnect you and ban you from their service.

(when I say connect I mean use it as a web server on their network - using the server to browse the internet should be fine)

Canon EF 28-135mm F/3.5-5.6 IS USM

06/22/2006 12:03:16 PM · #10

It isn't connected to the internet. It is just a home file server.

Nelzie

Canon EOS-30D

06/22/2006 12:05:10 PM · #11

Originally posted by SamDoe1:

Try using IE, might work better.

Never use IE, unless you are forced to by a bank or other commercial website you implicitly trust as good, real and not man-in-the-middle attacked at the moment. (Sorry that's my cranky IT Security side coming out.)

As for the server, what OS is running under Apache? Are you running Apache under Windows or some version of Linux or MacOSX or something else?

I have a similar slowness in speed with Apache on one of our Linux servers and that, I believe, has something to do with a few things. First, I do not have an internal DNS system setup, the server Apache is on, is also a fairly busy server in that it is regularly feeding Samba shares and our corporation's email and Squid Proxy server. (They won't kick out for another server right now, that's the only reason it is so busy.)

Beyond that, I haven't had reason to really look into tweaking Apache for speed on this server, as it isn't a primary application/system we use onsite.

Have you given the Apache mailing lists a look or check out the Apache FAQ? (There might be some notes in your Apache distro on tweaking it or the server, to provide faster Apache service.)

06/22/2006 12:11:35 PM · #12

Originally posted by Nelzie:

Originally posted by SamDoe1:
Try using IE, might work better.

Never use IE,

I don't use IE for anything other than Windows Update and, like you said, sites that don't allow anything else. But this was just an internal network transfer, so I didn't think it would matter from a security standpoint. Is this an incorrect assumption? Sorry to hijack, but I was just wondering.

06/22/2006 12:23:18 PM · #13

yes it is just an internal site so security is no issue.

I am running the server on a windows machine with
Mysql and Apache installed.

i think the speed i am getting is about 5 kbs. When I have tried to ftp to the computer it runs at that speed... very slow.. I should be able to get around 100 kbps

maxj

Canon EOS-300D Rebel

Canon EF 50mm f/1.8 II

06/22/2006 12:30:01 PM · #14

leaf, recently, I have come accross the problem you mentioned. It got bad enough that I couldnt even attempt to host my site localy anymore, and I now pay for my hosting.

I dont have any exact answers (im no expert), but, I can offer some theories (my old server works fine now...)

1. Your access/error log has become too big. At the time my server died, my current log file was 1 500 000 KB in size.

2. Poor scripting. Some of my PHP scripts would open streams, but never close them.

3. You're popular! I noticed a ridiculous slow down when my server took on more thatn one user. At the time of death, there were at least five user on my site at any given time.

hope maybe this helps? Good Luck!

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

06/22/2006 01:00:57 PM · #15

Originally posted by maxj:

1. my access/error log might be too big, but the server is pretty new so I don't think so
2. poor scripting.. a good chance, but that doesn't explain why ftp should go so slow.
3. mmm well since it is an internal server which only I can access I don' tthink anyone else is on that box. It is plain old just slow.

alfresco

Nikon D700

06/22/2006 01:12:08 PM · #16

What do you mean by 'slow'? A bit comes, waits a while, then some more comes, then wait a while ... -or- ... wait wait wait wait here comes some

first thought is dns, second is routing

make sure apache has hostnamelookups set to off (look in httpd.conf)

This will make apache *not* do dns lookups on your ip address

Message edited by author 2006-06-22 13:12:55.