I've been watching the internet tv for the past 9 months. CNN, FOX, NBC, etc all have their news online. It would be great if those were cachable. Just like on tv a lot of the news bits are over and over again and why should we have to keep paying each view.
The content providers like akamai, etc are valuable at this point. Dennis Burgess wrote: > MTs implementation is very simple. Not a whole lot to configure, but > thats what is great about it. Also, if your network is moving 250 gig > every 4 hours, that don't mean everything will be cached. ie. CNN has a > cache time of 0, so it won't be cached anyways. > > ------------------------------ > * Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer > Link Technologies, Inc -- Mikrotik & WISP Support Services* > 314-735-0270 > http://www.linktechs.net <http://www.linktechs.net/> > > */ Link Technologies, Inc is offering LIVE Mikrotik On-Line Training > <http://www.linktechs.net/onlinetraining.asp>/* > > > > Travis Johnson wrote: >> Hi, >> >> Are you somehow redirecting traffic to the MT box, or having all the >> traffic go through the box? >> >> Cache hit rates are going to depend on the size of the network... a >> 250GB drive would only cache about 4 hours of http traffic on my >> network... hit rates would be less than 5% I would guess. >> >> I've also heard MT doesn't work very well doing caching. Has this >> changed since v3 was released? >> >> Travis >> Microserv >> >> Dennis Burgess wrote: >>> You can do this as well with Mikrotik. >>> >>> MT is very, very simple. We have seen avg savings of between 20-40%. >>> With 25-30% being avg. Also, you can specify what sites you want to >>> cache, typically done by IP, but you could also say that you only want >>> to cache sites that are on different areas etc if you got the IP ranges >>> that you wanted to use. >>> >>> Something else, is that you can specify a bit for the cache hit data. >>> This means, you can throttle data that comes from your cache differently >>> than the customers standard package! So, data that comes from your >>> cache, maybe goes at full wireless speed etc. >>> >>> We usually drop in either a 80 gig or 250 gig SATA2 drive into our >>> PoweRouter 732s. If they have a large customer base, we drop in 2 gig >>> of ram just to be on the safe side. >>> >>> ------------------------------ >>> * Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer >>> Link Technologies, Inc -- Mikrotik & WISP Support Services* >>> 314-735-0270 >>> http://www.linktechs.net <http://www.linktechs.net/> >>> >>> */ Link Technologies, Inc is offering LIVE Mikrotik On-Line Training >>> <http://www.linktechs.net/onlinetraining.asp>/* >>> >>> >>> >>> David E. Smith wrote: >>> >>>>> What I'd LOVE to figure out how to set up is a spoke and hub cache system. >>>>> >>>>> >>>> Squid (and probably other caches) support something similar, in the form >>>> of parent and child caches. It sorta works backwards from what you >>>> described, but the net benefit would be similar. >>>> >>>> Basically, you set up caches at your POP locations, each of which is >>>> configured to use a bigger cache in your NOC as their "parent" cache. (Of >>>> course, you have to set up suitable firewalling at every tower, to >>>> redirect traffic from that POP's customers to the "local" cache.) >>>> >>>> Customer types in ebay.com, goes to their "local" cache. If the >>>> information they want isn't there, that cache checks with the big cache in >>>> your NOC. If it also doesn't have that page, it fetches it from the public >>>> Internet, and passes it on down. >>>> >>>> It's not a push system, but that's probably alright. I'm not sure how well >>>> a push system would work anyway. Anything like, say, the monthly crop of >>>> Windows Update downloads, they'd get spread out to the individual caches >>>> quickly enough anyway. >>>> >>>> David Smith >>>> MVN.net >>>> >>>> >>>> >>>> >>>> -------------------------------------------------------------------------------- >>>> WISPA Wants You! Join today! >>>> http://signup.wispa.org/ >>>> -------------------------------------------------------------------------------- >>>> >>>> WISPA Wireless List: wireless@wispa.org >>>> >>>> Subscribe/Unsubscribe: >>>> http://lists.wispa.org/mailman/listinfo/wireless >>>> >>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>> >>>> >>> >>> -------------------------------------------------------------------------------- >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> -------------------------------------------------------------------------------- >>> >>> WISPA Wireless List: wireless@wispa.org >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >>> >>> >>> >> ------------------------------------------------------------------------ >> >> >> >> -------------------------------------------------------------------------------- >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> -------------------------------------------------------------------------------- >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
