Re: [WISPA] Any thoughts on a decent cache server
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/
Re: [WISPA] Any thoughts on a decent cache server
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/
Re: [WISPA] Any thoughts on a decent cache server
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/
Re: [WISPA] Any thoughts on a decent cache server
Keep in mind that if you move 250 gig, that does not mean that it will cache that. CNN is an exaxmple that has a cache time of 0 seconds, so it never caches it.That type of thing.I have never had a major issue with MT caching services. Works VERY good. -- * 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/
Re: [WISPA] Any thoughts on a decent cache server
The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. Thats an easy one to fix. Tell them to press [CTRL] F5. Thats all it takes on virtually any standards compliant cache. The real pain is when shopping carts or the like do not work. We have had far better success having Mikrotik redirect/DST-NAT too Squid then using the Mikrotik cache. Far fewer websites with issues. Running the cache on Mikrotik really shot the CPU load up on the Mikrotik as well. Strange the CPU load on the box running Squid is barely anything. In the process of upgrading our network and bandwidth. Gonna try the Mikrotik cache again to see if its improved any. Its so much simpler doing it with an inline Mikrotik box. Matt 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/
Re: [WISPA] Any thoughts on a decent cache server
You can build a good squid box with lots of memory and fast hard drives and get good results. The squid setup is also nearly infinitely tunable, as opposed to the ones in Mikrotik and StarOS which have a pretty vanilla configuration. Being able to tune the cache parameters helps a lot, along with putting the cache directories on a separate hard drive and/or multiple ethernet cards to maximize the traffic flow. I have also used caching servers during heavy bandwidth demand or outage times to offload some of my browsing traffic to cable or dsl connections at the edges of the network. From a deployment perspective, I have gotten the best results by letting any questionable customers bypass the caches. 95% of my customers are on 192.168.0.0/16 addresses, so we had a rule that directed the /16 network to the cache. Customers with public IP addresses do not go through the cache. That way, someone with a problem going through the cache would have to upgrade to a static IP so that they could bypass it.Relatively simple, and effective. Matt Larsen vistabeam.com Matt wrote: The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. Thats an easy one to fix. Tell them to press [CTRL] F5. Thats all it takes on virtually any standards compliant cache. The real pain is when shopping carts or the like do not work. We have had far better success having Mikrotik redirect/DST-NAT too Squid then using the Mikrotik cache. Far fewer websites with issues. Running the cache on Mikrotik really shot the CPU load up on the Mikrotik as well. Strange the CPU load on the box running Squid is barely anything. In the process of upgrading our network and bandwidth. Gonna try the Mikrotik cache again to see if its improved any. Its so much simpler doing it with an inline Mikrotik box. Matt 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/
Re: [WISPA] Any thoughts on a decent cache server
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] Any thoughts on a decent cache server
In another attempt to light the bandwidth load we are going to setup a cache server. Any thoughts or suggestions on which one to use? __ Patrick Nix, Jr., csweb.net (918) 235-0414 http://www.csweb.net http://www.csweb.net/ E-Mail: [EMAIL PROTECTED] ATTENTION: This e-mail may contain information that is confidential in nature. If you are not the intended recipient, please delete this e-mail and notify the sender immediately. Thank you. 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/
Re: [WISPA] Any thoughts on a decent cache server
We used to have a caching server. You may also want to check out akamai They place their content servers at your noc so some content is closer to your customer. During dial up days we used both akamai and a squid caching server and it helped. Haven't done it for our bb system but also are going there soon again. George Patrick Nix Jr. wrote: In another attempt to light the bandwidth load we are going to setup a cache server. Any thoughts or suggestions on which one to use? __ Patrick Nix, Jr., csweb.net (918) 235-0414 http://www.csweb.net http://www.csweb.net/ E-Mail: [EMAIL PROTECTED] ATTENTION: This e-mail may contain information that is confidential in nature. If you are not the intended recipient, please delete this e-mail and notify the sender immediately. Thank you. 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/
Re: [WISPA] Any thoughts on a decent cache server
Patrick Nix Jr. wrote: In another attempt to light the bandwidth load we are going to setup a cache server. Any thoughts or suggestions on which one to use? I know this is the popular answer to everything on this list, but Mikrotik RouterOS has a decent, and dead-simple to use, proxy/cache package. The tricky part is probably finding the right place in your network to put it, and configuring firewall rules (so that Web traffic gets sent to the proxy/cache server), and even those aren't too difficult. At least the old one was pretty good - my experience with it was probably four years ago, but at the time it worked well. Between then and now, I believe Mikrotik has written their own (previously it was just the Squid open-source package, with their pretty interface on top). If you're comfortable with Linux, you can do it yourself, but the time you'll save is easily worth the low one-time cost of a RouterOS software license. Whatever you use, make sure you know how to handle exceptions. Some Web sites just don't play well with being proxied. (One of our customers is a dealer for a major auto maker, and the proxy/cache system basically killed their whole business, as the stuff in Detroit just flat refused to function.) You'll want an easy way to test this sort of thing at your desktop, to try to reproduce weird customer calls - and there will be some doozies. 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/
Re: [WISPA] Any thoughts on a decent cache server
So is it safer/better to avoid caching servers altogether? __ Patrick Nix, Jr., csweb.net (918) 235-0414 http://www.csweb.net E-Mail: [EMAIL PROTECTED] ATTENTION: This e-mail may contain information that is confidential in nature. If you are not the intended recipient, please delete this e-mail and notify the sender immediately. Thank you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David E. Smith Sent: Thursday, July 10, 2008 1:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server Patrick Nix Jr. wrote: In another attempt to light the bandwidth load we are going to setup a cache server. Any thoughts or suggestions on which one to use? I know this is the popular answer to everything on this list, but Mikrotik RouterOS has a decent, and dead-simple to use, proxy/cache package. The tricky part is probably finding the right place in your network to put it, and configuring firewall rules (so that Web traffic gets sent to the proxy/cache server), and even those aren't too difficult. At least the old one was pretty good - my experience with it was probably four years ago, but at the time it worked well. Between then and now, I believe Mikrotik has written their own (previously it was just the Squid open-source package, with their pretty interface on top). If you're comfortable with Linux, you can do it yourself, but the time you'll save is easily worth the low one-time cost of a RouterOS software license. Whatever you use, make sure you know how to handle exceptions. Some Web sites just don't play well with being proxied. (One of our customers is a dealer for a major auto maker, and the proxy/cache system basically killed their whole business, as the stuff in Detroit just flat refused to function.) You'll want an easy way to test this sort of thing at your desktop, to try to reproduce weird customer calls - and there will be some doozies. 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/
Re: [WISPA] Any thoughts on a decent cache server
We have quite a few PoweRouter 732s running Caching on networks. 1000+ users in some cases. -- * 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/* Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? __ Patrick Nix, Jr., csweb.net (918) 235-0414 http://www.csweb.net E-Mail: [EMAIL PROTECTED] ATTENTION: This e-mail may contain information that is confidential in nature. If you are not the intended recipient, please delete this e-mail and notify the sender immediately. Thank you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David E. Smith Sent: Thursday, July 10, 2008 1:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server Patrick Nix Jr. wrote: In another attempt to light the bandwidth load we are going to setup a cache server. Any thoughts or suggestions on which one to use? I know this is the popular answer to everything on this list, but Mikrotik RouterOS has a decent, and dead-simple to use, proxy/cache package. The tricky part is probably finding the right place in your network to put it, and configuring firewall rules (so that Web traffic gets sent to the proxy/cache server), and even those aren't too difficult. At least the old one was pretty good - my experience with it was probably four years ago, but at the time it worked well. Between then and now, I believe Mikrotik has written their own (previously it was just the Squid open-source package, with their pretty interface on top). If you're comfortable with Linux, you can do it yourself, but the time you'll save is easily worth the low one-time cost of a RouterOS software license. Whatever you use, make sure you know how to handle exceptions. Some Web sites just don't play well with being proxied. (One of our customers is a dealer for a major auto maker, and the proxy/cache system basically killed their whole business, as the stuff in Detroit just flat refused to function.) You'll want an easy way to test this sort of thing at your desktop, to try to reproduce weird customer calls - and there will be some doozies. 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/
Re: [WISPA] Any thoughts on a decent cache server
Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/
Re: [WISPA] Any thoughts on a decent cache server
When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/ inline: ctilogo200.jpg Bo Ring Account Manager [EMAIL PROTECTED] cell: 630-743-1162 • office: 312-205-2515 16W235 83rd Street, Suite A, Burr Ridge, IL 60527 • tel: 773.667.4585 fax: 773.326.4641 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/
Re: [WISPA] Any thoughts on a decent cache server
Not IMHO, You can just bypass the caching server for sites that give you trouble. I've had to by pass 3 or 4 so far. We only cache HTTP. One of our towers average bandwidth to the internet dropped from around 5Mbps to around 3Mbps and after 3 weeks up it has cached over 55GB. Mikrotik also lets you bypass bandwidth queues for cached data so subs get the pages fast. We use a Powerouter 732 as the core router at this tower and have a 250GB drive in it. We first tried dropping a cheap box plugged into a 532a but the CPU was hammered by the packets coming in one one interface, going out to the cache box, and coming back in the router, then going back out the interface connected to the radios. Caching with the router itself has really helped a lot. Jim jeffcosoho.com Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? __ Patrick Nix, Jr., csweb.net (918) 235-0414 http://www.csweb.net E-Mail: [EMAIL PROTECTED] ATTENTION: This e-mail may contain information that is confidential in nature. If you are not the intended recipient, please delete this e-mail and notify the sender immediately. Thank you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David E. Smith Sent: Thursday, July 10, 2008 1:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server Patrick Nix Jr. wrote: In another attempt to light the bandwidth load we are going to setup a cache server. Any thoughts or suggestions on which one to use? I know this is the popular answer to everything on this list, but Mikrotik RouterOS has a decent, and dead-simple to use, proxy/cache package. The tricky part is probably finding the right place in your network to put it, and configuring firewall rules (so that Web traffic gets sent to the proxy/cache server), and even those aren't too difficult. At least the old one was pretty good - my experience with it was probably four years ago, but at the time it worked well. Between then and now, I believe Mikrotik has written their own (previously it was just the Squid open-source package, with their pretty interface on top). If you're comfortable with Linux, you can do it yourself, but the time you'll save is easily worth the low one-time cost of a RouterOS software license. Whatever you use, make sure you know how to handle exceptions. Some Web sites just don't play well with being proxied. (One of our customers is a dealer for a major auto maker, and the proxy/cache system basically killed their whole business, as the stuff in Detroit just flat refused to function.) You'll want an easy way to test this sort of thing at your desktop, to try to reproduce weird customer calls - and there will be some doozies. 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/
Re: [WISPA] Any thoughts on a decent cache server
I call that 1% the high-maintenance customers . Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/
Re: [WISPA] Any thoughts on a decent cache server
The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. But still it's a phone call and a discussion. Kurt Fankhauser wrote: I call that 1% the high-maintenance customers . Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/
Re: [WISPA] Any thoughts on a decent cache server
I'd like to mention there could be other good benefits for caching. For example, It can be beneficial to cache sites that are geographically far away. The farther a site is away the more latency it has, and there fore the speed per session diminishes, based on the formula like window size = bandwidth * delay. . TCP throughput vs. window size for RTT=70ms Window Size Theoretical max throughput Realistic throughput 8KB 0.9Mb/s 0.8Mb/s 16KB 1.9Mb/s 1.8Mb/s 32KB 3.7Mb/s 2-3.5Mb/s 64KB 7.5Mb/s 3-7Mb/s 128KB 15.0Mb/s 6-14Mb/s 256KB 30.0Mb/s 10-25Mb/s 512KB 59.9Mb/s 20-40Mb/s 1MB 119.8Mb/s 30-60Mb/s 2MB 239.7Mb/s 60-100Mb/s What often occurs is that Window Size is fixed at the customer PC. So even if someone has a 100mbps connection, and can test 100mbps to their server across town 5 ms away, there speed is still severally limited to far away high latency sites. Many PCs by default, don't enable window sizes above 64k. (Although most newer XP/VISTA machines are now comming Registry optimized for automatic tuning of larger windows szies, so this isn;t a problem.) So its not just about cost of long haul bandwdith, but also desire to deliver full speed to the consumer. By caching data locally, it enables the customer to access it at the full broadband connection speed. But my point being, customers can get a much better perception of performance if the most common files to download were cached locally for retrieval. What I'd be interested in learning more on is how to setup a caching server to selectively select what to cache based on latency to the content, or most common data, apposed to just caching everything. In otherwords, how to optimize the chance that the benefit of caching will outweigh the chances of getting troubles from caching. Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Bo Ring [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 3:07 PM Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/ Bo Ring Account Manager [EMAIL PROTECTED] cell: 630-743-1162 . office: 312-205-2515 16W235 83rd Street, Suite A, Burr Ridge, IL 60527 . tel: 773.667.4585 fax: 773.326.4641 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/
Re: [WISPA] Any thoughts on a decent cache server
I don't know if it's better now, but when I tried to use MT as a cache it REALLY slowed things down. Speeds were higher, but the time from click to page start went up a LOT. So the internet FELT much slower. I loved my old Cobalt CacheRAQ. Wish I could find something like that again. It worked very well and was really easy to configure, adjust. marlon - Original Message - From: David E. Smith [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 11:07 AM Subject: Re: [WISPA] Any thoughts on a decent cache server Patrick Nix Jr. wrote: In another attempt to light the bandwidth load we are going to setup a cache server. Any thoughts or suggestions on which one to use? I know this is the popular answer to everything on this list, but Mikrotik RouterOS has a decent, and dead-simple to use, proxy/cache package. The tricky part is probably finding the right place in your network to put it, and configuring firewall rules (so that Web traffic gets sent to the proxy/cache server), and even those aren't too difficult. At least the old one was pretty good - my experience with it was probably four years ago, but at the time it worked well. Between then and now, I believe Mikrotik has written their own (previously it was just the Squid open-source package, with their pretty interface on top). If you're comfortable with Linux, you can do it yourself, but the time you'll save is easily worth the low one-time cost of a RouterOS software license. Whatever you use, make sure you know how to handle exceptions. Some Web sites just don't play well with being proxied. (One of our customers is a dealer for a major auto maker, and the proxy/cache system basically killed their whole business, as the stuff in Detroit just flat refused to function.) You'll want an easy way to test this sort of thing at your desktop, to try to reproduce weird customer calls - and there will be some doozies. 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/
Re: [WISPA] Any thoughts on a decent cache server
No way. I'm pretty sure I'm gonna put one on again. Back when I used one it saved me 25% or so on bandwidth. It also made the internet FEEL faster. I want to cache MS updates, youtube and expecially MSN and other high content sites that otherwise suck to use. marlon - Original Message - From: Patrick Nix Jr. [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 11:53 AM Subject: Re: [WISPA] Any thoughts on a decent cache server So is it safer/better to avoid caching servers altogether? __ Patrick Nix, Jr., csweb.net (918) 235-0414 http://www.csweb.net E-Mail: [EMAIL PROTECTED] ATTENTION: This e-mail may contain information that is confidential in nature. If you are not the intended recipient, please delete this e-mail and notify the sender immediately. Thank you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David E. Smith Sent: Thursday, July 10, 2008 1:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server Patrick Nix Jr. wrote: In another attempt to light the bandwidth load we are going to setup a cache server. Any thoughts or suggestions on which one to use? I know this is the popular answer to everything on this list, but Mikrotik RouterOS has a decent, and dead-simple to use, proxy/cache package. The tricky part is probably finding the right place in your network to put it, and configuring firewall rules (so that Web traffic gets sent to the proxy/cache server), and even those aren't too difficult. At least the old one was pretty good - my experience with it was probably four years ago, but at the time it worked well. Between then and now, I believe Mikrotik has written their own (previously it was just the Squid open-source package, with their pretty interface on top). If you're comfortable with Linux, you can do it yourself, but the time you'll save is easily worth the low one-time cost of a RouterOS software license. Whatever you use, make sure you know how to handle exceptions. Some Web sites just don't play well with being proxied. (One of our customers is a dealer for a major auto maker, and the proxy/cache system basically killed their whole business, as the stuff in Detroit just flat refused to function.) You'll want an easy way to test this sort of thing at your desktop, to try to reproduce weird customer calls - and there will be some doozies. 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/
Re: [WISPA] Any thoughts on a decent cache server
I totally disagree with that David. A cache server will often make yahoo and other common sites load in MUCH less time. There won't be much real change in speeds (like when doing a bw test) but the look and feel will be much better. marlon - Original Message - From: David E. Smith [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 1:03 PM Subject: Re: [WISPA] Any thoughts on a decent cache server Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/
Re: [WISPA] Any thoughts on a decent cache server
When we had that trouble we just had to teach them to use the shift, refresh trick. forced the cache to load the new page now instead of when it normally would have. No trouble with them after that. marlon - Original Message - From: George Rogato [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 8:27 PM Subject: Re: [WISPA] Any thoughts on a decent cache server The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. But still it's a phone call and a discussion. Kurt Fankhauser wrote: I call that 1% the high-maintenance customers . Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/
Re: [WISPA] Any thoughts on a decent cache server
Hi, Back when we tried the cache server thing (5 years ago), it turned into more work than it was worth. We were getting 2-3 calls per day from people that certain web pages were broken and not loading correctly, etc. The real kicker was when UPS shut down our cache server's IP address because they thought we were doing "too many shipping lookups from the same IP address". Turns out one of our bigger customers was the main distributor for DISH Network and their automated system did a lookup on UPS's website whenever anyone was tracking a shipment. In the end, they canceled service ($500/month) because of this. Bandwidth is cheap now-a-days, even in Idaho (where the closest POP is 200+ miles). A cache server is just going to add headaches, support calls, and one more server(s) to maintain. Travis Microserv Marlon K. Schafer wrote: When we had that trouble we just had to teach them to use the "shift, refresh" trick. forced the cache to load the new page now instead of when it normally would have. No trouble with them after that. marlon - Original Message - From: "George Rogato" [EMAIL PROTECTED] To: "WISPA General List" wireless@wispa.org Sent: Thursday, July 10, 2008 8:27 PM Subject: Re: [WISPA] Any thoughts on a decent cache server The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. But still it's a phone call and a discussion. Kurt Fankhauser wrote: I call that 1% the "high-maintenance customers ". Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/
Re: [WISPA] Any thoughts on a decent cache server
use the shift, refresh trick. That was a helpful tip. Is that just an IE6 thing? Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 10:49 PM Subject: Re: [WISPA] Any thoughts on a decent cache server When we had that trouble we just had to teach them to use the shift, refresh trick. forced the cache to load the new page now instead of when it normally would have. No trouble with them after that. marlon - Original Message - From: George Rogato [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 8:27 PM Subject: Re: [WISPA] Any thoughts on a decent cache server The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. But still it's a phone call and a discussion. Kurt Fankhauser wrote: I call that 1% the high-maintenance customers . Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/
Re: [WISPA] Any thoughts on a decent cache server
Don't know. It was a specific tip from the folks that made my cache. Don't know if it works on others. Caching is on my short list of network upgrades to do. The bigger the network is the more good it does. marlon - Original Message - From: Tom DeReggi [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 9:14 PM Subject: Re: [WISPA] Any thoughts on a decent cache server use the shift, refresh trick. That was a helpful tip. Is that just an IE6 thing? Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 10:49 PM Subject: Re: [WISPA] Any thoughts on a decent cache server When we had that trouble we just had to teach them to use the shift, refresh trick. forced the cache to load the new page now instead of when it normally would have. No trouble with them after that. marlon - Original Message - From: George Rogato [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 8:27 PM Subject: Re: [WISPA] Any thoughts on a decent cache server The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. But still it's a phone call and a discussion. Kurt Fankhauser wrote: I call that 1% the high-maintenance customers . Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/ 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/
Re: [WISPA] Any thoughts on a decent cache server
Tom, You can find all kinds of information if you do searches on squid. It's a very popular caching system that runs on *nix. The amount of RAM is directly related to the size of the disk cache. When we had servers 5 years ago (two of them in parallel) they were the fastest processors you could buy, with SCSI disk arrays in each one and I think 2GB of RAM each. I would guess in today's world you would be looking at 8GB or 16GB of RAM and very large disk arrays (6 disks x 500GB maybe). The other thing to consider is you now have another point of failure in your network. If a disk starts acting strange or the machine does a core dump, whatever you have re-directing traffic to the box may take 5 seconds to realize it's down and not send traffic to it. If you put it directly in-line with your traffic flow, you will have a complete failure of all internet services to your customers. :( Travis Microserv Tom DeReggi wrote: Any stats, on how much RAM is a good amount to allocated for the cache servers, per user served? Obviously, a large fast DiskDrive, is needed if caching a lot of large files. I'd also argue that DiskDrive probably should be located on a dedicated appliance. Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: "Marlon K. Schafer" [EMAIL PROTECTED] To: "WISPA General List" wireless@wispa.org Sent: Thursday, July 10, 2008 10:49 PM Subject: Re: [WISPA] Any thoughts on a decent cache server When we had that trouble we just had to teach them to use the "shift, refresh" trick. forced the cache to load the new page now instead of when it normally would have. No trouble with them after that. marlon - Original Message - From: "George Rogato" [EMAIL PROTECTED] To: "WISPA General List" wireless@wispa.org Sent: Thursday, July 10, 2008 8:27 PM Subject: Re: [WISPA] Any thoughts on a decent cache server The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. But still it's a phone call and a discussion. Kurt Fankhauser wrote: I call that 1% the "high-maintenance customers ". Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/w
Re: [WISPA] Any thoughts on a decent cache server
Shift R means it won't take it from your computers cache. But it still going to hit your caching server. Your right Marlon those cobalt servers were pretty cool. Sun bought them didn't they? George Marlon K. Schafer wrote: Don't know. It was a specific tip from the folks that made my cache. Don't know if it works on others. Caching is on my short list of network upgrades to do. The bigger the network is the more good it does. marlon - Original Message - From: Tom DeReggi [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 9:14 PM Subject: Re: [WISPA] Any thoughts on a decent cache server use the shift, refresh trick. That was a helpful tip. Is that just an IE6 thing? Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 10:49 PM Subject: Re: [WISPA] Any thoughts on a decent cache server When we had that trouble we just had to teach them to use the shift, refresh trick. forced the cache to load the new page now instead of when it normally would have. No trouble with them after that. marlon - Original Message - From: George Rogato [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 8:27 PM Subject: Re: [WISPA] Any thoughts on a decent cache server The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. But still it's a phone call and a discussion. Kurt Fankhauser wrote: I call that 1% the high-maintenance customers . Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/ 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
Re: [WISPA] Any thoughts on a decent cache server
The drive should be big. But probably doesn't need to be that big. Remember that a drive is MUCH faster than the average network. I'd guess that it would be hard to have too much ram or proc. marlon - Original Message - From: Tom DeReggi [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 9:18 PM Subject: Re: [WISPA] Any thoughts on a decent cache server Any stats, on how much RAM is a good amount to allocated for the cache servers, per user served? Obviously, a large fast DiskDrive, is needed if caching a lot of large files. I'd also argue that DiskDrive probably should be located on a dedicated appliance. Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 10:49 PM Subject: Re: [WISPA] Any thoughts on a decent cache server When we had that trouble we just had to teach them to use the shift, refresh trick. forced the cache to load the new page now instead of when it normally would have. No trouble with them after that. marlon - Original Message - From: George Rogato [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 8:27 PM Subject: Re: [WISPA] Any thoughts on a decent cache server The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. But still it's a phone call and a discussion. Kurt Fankhauser wrote: I call that 1% the high-maintenance customers . Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/ 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/
Re: [WISPA] Any thoughts on a decent cache server
What I'd LOVE to figure out how to set up is a spoke and hub cache system. Let the MAIN site track the sites, then feed that data to all of the wpops. This way we'd keep most of the traffic of the internet (great to get content in single digit ms speeds rather than mid to high double digit ones) and we'd not have to have all of the traffic go back to the main site all of the time. But cache's don't work well for small, low volume sites. Oh well, another project for someday. marlon - Original Message - From: Travis Johnson To: WISPA General List Sent: Thursday, July 10, 2008 9:21 PM Subject: Re: [WISPA] Any thoughts on a decent cache server Tom, You can find all kinds of information if you do searches on squid. It's a very popular caching system that runs on *nix. The amount of RAM is directly related to the size of the disk cache. When we had servers 5 years ago (two of them in parallel) they were the fastest processors you could buy, with SCSI disk arrays in each one and I think 2GB of RAM each. I would guess in today's world you would be looking at 8GB or 16GB of RAM and very large disk arrays (6 disks x 500GB maybe). The other thing to consider is you now have another point of failure in your network. If a disk starts acting strange or the machine does a core dump, whatever you have re-directing traffic to the box may take 5 seconds to realize it's down and not send traffic to it. If you put it directly in-line with your traffic flow, you will have a complete failure of all internet services to your customers. :( Travis Microserv Tom DeReggi wrote: Any stats, on how much RAM is a good amount to allocated for the cache servers, per user served? Obviously, a large fast DiskDrive, is needed if caching a lot of large files. I'd also argue that DiskDrive probably should be located on a dedicated appliance. Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 10:49 PM Subject: Re: [WISPA] Any thoughts on a decent cache server When we had that trouble we just had to teach them to use the shift, refresh trick. forced the cache to load the new page now instead of when it normally would have. No trouble with them after that. marlon - Original Message - From: George Rogato [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 8:27 PM Subject: Re: [WISPA] Any thoughts on a decent cache server The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. But still it's a phone call and a discussion. Kurt Fankhauser wrote: I call that 1% the high-maintenance customers . Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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
Re: [WISPA] Any thoughts on a decent cache server
Yeah. I don't think they do any cache units anymore. marlon - Original Message - From: George Rogato [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 9:22 PM Subject: Re: [WISPA] Any thoughts on a decent cache server Shift R means it won't take it from your computers cache. But it still going to hit your caching server. Your right Marlon those cobalt servers were pretty cool. Sun bought them didn't they? George Marlon K. Schafer wrote: Don't know. It was a specific tip from the folks that made my cache. Don't know if it works on others. Caching is on my short list of network upgrades to do. The bigger the network is the more good it does. marlon - Original Message - From: Tom DeReggi [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 9:14 PM Subject: Re: [WISPA] Any thoughts on a decent cache server use the shift, refresh trick. That was a helpful tip. Is that just an IE6 thing? Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 10:49 PM Subject: Re: [WISPA] Any thoughts on a decent cache server When we had that trouble we just had to teach them to use the shift, refresh trick. forced the cache to load the new page now instead of when it normally would have. No trouble with them after that. marlon - Original Message - From: George Rogato [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Thursday, July 10, 2008 8:27 PM Subject: Re: [WISPA] Any thoughts on a decent cache server The people that we had the most problems with were web designers who's sites were cached and they couldn't easily see their changes. We always told then to add no cache to their sites. But still it's a phone call and a discussion. Kurt Fankhauser wrote: I call that 1% the high-maintenance customers . Kurt Fankhauser WAVELINC P.O. Box 126 Bucyrus, OH 44820 419-562-6405 www.wavelinc.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bo Ring Sent: Thursday, July 10, 2008 4:07 PM To: WISPA General List Subject: Re: [WISPA] Any thoughts on a decent cache server When I was an ISP, that 1% got me in real trouble. They scream loudly. On Jul 10, 2008, at 3:03 PM, David E. Smith wrote: Patrick Nix Jr. wrote: So is it safer/better to avoid caching servers altogether? About 99% of your users won't notice, or know, or care, that you've got anything like that in your network. The savings in bandwidth (and, to a lesser extent, money not spent on bandwidth) can help you out of a tight spot. Just be aware that the last 1% of customers can get you into trouble. 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/ WISPA Wants You
