I'll put in another encouraging note on WAN accelerators. I last looked
at this 5 years ago, and I'm sure things have improved a lot since then,
but these things are generally mature and solid. There are many options
which may or may not work based upon your specific needs. Some have
large local RAM and disk cache for pattern matching and latency
reduction, some just do TCP compression and early ack.
Depending upon if the files that are being accessed are frequently
accessed in NL, you could get significant mileage out of the caching
devices. The premise is that you put one on each end. When you request
the file, the local side sees the request, notices that it is a file
that it has buffered, and sends it immediately out of cache after
verifying that there haven't been changes by contacting the local
server. There can also be bandwidth reduction this way..
client --- cache device A ------------wan ----------------cache device
B------- server
Let's say client wants file from server. The default route goes through
cache device A which then goes over WAN normally to server. Server
responds with a bunch of bytes. cache device B says "hey, I recognize
this bunch of bytes. I've sent it before". It sends an inline identifier
to cache device A. Cache device A looks up the identifier and sends the
full bucket of bytes over to client. In that mode, it works as a WAN
compression appliance. There's more than one way to do that, too..
Doug
_______________________________________________
Discuss mailing list
Discuss@lopsa.org
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
