General discussion

Locked

High dollar low performance network

By azul ·
I work for a large healthcare facility that spends a lot of money on its network and on technology in general. Everything looks and sounds really good, but in reality, the network performance sucks. Remote administration task that should only take a minute or two takes an half an hour. This is a constant problem everywhere. Is this typical for a facility with a large network?

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Bottlenecks

by jdmercha In reply to High dollar low performan ...

Spending money does not necessarily equate to quality equipment. Then again "Performance sucks" is rather objective. What are kind of performance were you expecting?

Look for bottlenecks. There can be many devices and networks in the way of "remote administration". It only takes one of them to slow down the whole works.

Collapse -

Additionally ...

by stress junkie In reply to Bottlenecks

As implied by jdmercha's brief response, network design is critical to performance. It is possible that you could improve network performance by segregating paths of network traffic. For instance the accounting department probably just needs to connect to the accounting server. If the accounting department had an unshared network path to the accounting computers then they would not have to share the network bandwidth with the personnel department and with the patient records server. There is a good chance that you could improve network response by adding a few lengths of cables to your current network and configuring bridges, routers, and internal firewalls to physically separate the network traffic of different departments or other groups.

Also, as jdmercha stated, there is a limit to any given configuration so it really depends on how people are using the network. If you have got good equipment, which is often expensive but not necessarily so, then a simple network should be able to support a fairly large amount of traffic. I don't want to specify a number of users because it all depends on what the users are transmitting over the network. If doctors are transmitting huge digitised files of CAT scans all day then they will easily use up network bandwidth. One doctor or radiologist could overwhelm most networks for several minutes by transmitting one huge file. This kind of traffic probably should be segregated onto it's own wiring. However a simple high bandwidth network should be able to accomodate many secretaries doing typical office work.

So there you are. You have to understand your network traffic and the network configuration before you can decide if reconfiguring what you have will help or if you need to add hardware.

Back to Community Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums