General discussion

Locked

How super is super speed network design?

By bg22 ·
We have a server farm on the Internet. Roughly 20 servers. 8 Are on the segment connected to the internet (DMZ Segment), All computers are connected to a second back end network (the computers connected to the front-end segment have 2 NIC cards). The back end segment is Gigabit. All servers are running Windows 2000.

The front-end web/app servers communicate to the databases via the back-end segment. In addition, large files are impoted/exported and frequently moved among various servers on both the front-end and those on the back-end (very large PDF files are being assembled on the fly on the backend by pulling high resolution images from various other servers and then positioning these for user download on other servers.

Trafficsummary during peak hours:
- small file traffic between front-end web/app servers and database servers (100,000 transmissions/hour ave. 1KB in and 50KB out) These need instantaneous response.
- medium file movement (files between 500KB and 1MB) about 10,000/hour. These do not have to move immediately.
- large file movement (files 10MB - 200MB) about 100 hour. These do not have to move immediately.

The concern is that the large low priority file transfers could congest the back-end segment and cause delay for the small, high priority web/app server - database interaction.

One school has suggested we add a second back-end segment for the movement of the large low priority files and leave the main segment for smaller, high priority transmission.

The other school says Gigabit is so large that we would not even notice the large file transfers.

I need some more opinions on this.

Thanks in advance.

This conversation is currently closed to new comments.

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

All Comments

Collapse -

How super is super speed network design?

by TimTheToolMan In reply to How super is super speed ...

Hi,

It really depends on specifically how you've got the DMZ and internal backbone connections configured (through the 2K machines).

The Gigabit link itself will be fast enough to service all the traffic comfortably, but your bottleneck will be at the 2K servers that are acting as routers to your DMZ.

How fast are the nics in those machines? Will the load be equally distributed between them? Will the machines themselves be able to keep up with the simple routing function?

And finally do I have the overall picture right in the first place? :-)

Cheers
Tim.

Collapse -

How super is super speed network design?

by bg22 In reply to How super is super speed ...

Almost all the large file traffic is traffic among the servers themselves and never goes to the outside. Only the smaller files go to the outside customers through 3 web server running Microsoft ASP. We can add additional web/appservers as needed. The concern is that the other traffic sharing the same back-end network would get in the way of the traffic between the database and web servers (we often have to move MBs to provide a 10K answer and yet keep response time to the browser client in the 2-3 second range).

Collapse -

How super is super speed network design?

by wlbowers In reply to How super is super speed ...

A second back-end with load share shure
wouldn't hurt. Everything should be Gigabit.

Everything revolves around the numbers.
Remember the files aren't the only data going
down the pike.

Good Luck Lee

Back to Networks Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums