|
|
|
| Hey all,
On one of our web servers we have around 8 gigs of song. We have dsl and even the local network is based on dsl.To access that server means a solid affect on the upload speed even though we are internals.And besides the major chunk of speed is taken by the websites and we are not able to play any songs from that server.Is there any way to workaorund this or is there any way of caching.
Thanx and Regards | |
| Nicole 2001-12-20, 3:02 pm |
| How is your local network "based on DSL"? Is the server in a remote location? | |
|
| The server is not on a remote location. The internal network is itself working thru the dsl router i.e even though the machines are in the same room if i access computer1 from computer2 i am using the dsl download speed for computer2 and dsl upload speed from computer1.
Hope i did not confuse you. | |
| Nicole 2001-12-20, 4:25 pm |
| I don't understand why they would have choosen to route through the DSL box... isn't there a hub? Or an I misunderstanding?
Is it like this:
incoming DSL line
|
DSL ROUTER -- CLIENTS
|
SERVER
Or like this:
incoming DSL line
|
DSL ROUTER
|
NETWORK HUB -- CLIENTS
|
SERVER | |
|
| hey its like this...
incoming dsl line
|
dslRouter
|
Clients/independent workstations
The infrastructure is not of a main server and clients. Each client is independent but on the same netowrk/domain. Its more like a peer to peer.
So if one machine on network tries to access the songs from the machine that has songs, due to the heavy load that comes on the network it's not possible.
So is there any way to fasten up or cache the songs folder for fast access. | |
| Nicole 2001-12-20, 5:58 pm |
| quote: Each client is independent but on the same netowrk/domain. Its more like a peer to peer.
Is it like peer to peer or is it peer to peer? (Sorry... couldn't resist.)
I don't know what you are defining as heavy network load, or what the network size is, but there seems to be a simple solution -- send your office manager down to Staples with $30 and buy a 10/100 hub and an extra RJ45 cable.
Even without a client/server architecture, I don't see why this wouldn't eliminate your bottleneck and allow internal connection to run up to the maximum speed your network cards will allow.
P.S. A web server running off DSL? They must be braver than me... | |
|
| Good piece of advice. I will follow that
but...
lemme show u a different picture.
Suppose
I have a server running on an i.p 10.10.10.10. On this server a folder is shared as Songs. U have the permisions to access that folder and u access it at 10.10.10.10/songs.
Since the upload speed of the server is consumed by other stuff running on it, it creates a problem for u to listen to songs. what do u recommend.
Thanks  | |
| Nicole 2001-12-20, 8:36 pm |
| Got me. I still don't understand the concept of why anyone would want to run their network on DSL. Hubs are cheap. Even good hubs are cheap. I just don't get it.
Since MOST businesses would not include listening to songs at work as part of the business requirements, I'd eliminate the problem by getting rid of the songs.
For those businesses that DO need good access to multimedia (like songs), I'd suggest implementation of the proper hardware and network configuration to handle the bandwidth Actually, I'd suggest the proper network hardware anyway. What happens if your DSL line goes out... as they frequently do? Do you also loose all of your internal network? Why are you routing internal traffic over the internet and your DSL provider anyway? So many things to go wrong... so many places to get hacked...
For businesses that require the ability to service multimedia over the internet, I'd start with eliminating a cheesy DSL line (let alone your ADSL line!) and investing in the dedicated leased line access that can handle the bandwidth, like a fractional T1 or better, which can be upgraded as needed.
BUT --
Since I have the feeling the issue is really a certain IT person's extracurricular activities at work --
I'd spread your data over multiple physical drives to improve access time. It won't fix the DSL bottleneck, but it might be a little improvement. Even spreading the data among the node might help by blurring the upload/download issue.
Anyone else want to chime in here? | |
|
| "BUT --
Since I have the feeling the issue is really a certain IT person's extracurricular activities at work -- "
Caught me  | |
| darthw 2001-12-21, 3:43 pm |
| We had a tech where I once worked using the LAN for similar extracurricular activity. He too set up disk striping in order to deal with some access speed issues on a music/multimedia server. I don't know that it helped a ton in his case, but theoretically you should see some improvement.
Also, why not get a 10/100 Ether switch (not a hub) and chain it off the DSL router, then connect this music server, and the other client workstations to the switch. A switch will give each client dedicated bandwidth instead of everyone sharing the bandwidth as a hub will do. | |
| Nicole 2001-12-21, 4:06 pm |
| Just a thought -- are you sharing these song files (MP3?) over the internet, ala Gnutella or pre-lawsuit Napster? If you are, that could REALLY be taking a chunk out of your bandwidth!
Darth -- the switch is a good idea. It won't improve access time to the songs, but it will prevent the rest of the network from getting bogged down.
I have a hunch that Akhan can't get approval to buy anything because he can't justify it
Akhan, tell your IT manager/VP/office manager/whomever that you need a hub (or a switch, but they cost more money) for security reasons. Your internal communications are getting routed through the internet without the appropriate encryption. The addition of one small, inexpensive piece of hardware will increase your network security and prevent a very costly security breach. |
|
|
|