Astaro User Bulletin Board
Go Back   Astaro User Bulletin Board > Astaro Gateway Products > Web Security: HTTP/HTTPS/FTP, IM/P2P, Web Filtering and Antivirus

Welcome to the Astaro User Bulletin Board.
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 07-26-2008, 06:05 PM
Billybob's Avatar
Wizard
 
Join Date: Jul 2006
Location: United States
Posts: 637
Default HTTP Proxy Cache size

Recently upgraded from astaro 6.xx to 7.21. Hardware P4 2GHZ core duo 250gb hdd, 2 gb ram.

I have been running fine for a while, logged into the console just to see how everything was running and noticed that the proxy cache is at 17M. Let the http proxy run for about a week and its still at 17M. Is this normal? In astaro 6.3x under var/chroot-squid the cache was a few hundered megs. Under 7.21 under var/chroot-http, the cache is only 17M, I guess by design. Was wondering if I am the only one seeing this
Reply With Quote
  #2 (permalink)  
Old 07-27-2008, 11:16 AM
Moderator
 
Join Date: Jul 2001
Location: southern California
Posts: 5,148
Default

How big is the 'storage' partition?

df -h

Barry
__________________
http://DealBert.net
Home & business end-user since v1.x
  • ASL 6.3x, HP DL145 Dual Opteron, 1GB RAM, 6 gigE NICs, 50-IP Platinum License
  • ASL 7.3x, Dell PE1550 Dual PIII 1GHz, 1GB RAM, 2 NICs, 50-IP Platinum License
  • ASL 7.5x, 17-watt fanless mini-ITX system: MSI IM-945GSE-A Atom n270, 2GB RAM, Morex T3310 case. 2 Intel GigE, 3 VLANs. 80G 5200rpm 2.5" HD
    Netgear GS108T gigE VLAN switch & Linksys WRT54G WAP
    Total network infrastructure: 27 watts. 100-IP Home User. FiOS 10mb/2mb
Reply With Quote
  #3 (permalink)  
Old 07-27-2008, 05:35 PM
Billybob's Avatar
Wizard
 
Join Date: Jul 2006
Location: United States
Posts: 637
Default

/dev/disk/by-label/storage
75G 480M 74G 1% /var/storage

So no problem for space. Buth du -ch |grep total of /var/chroot-http/var/cache directory still yields 17M

Could you check your cache directory and see what the size is?
Thanks Barry
Reply With Quote
  #4 (permalink)  
Old 07-28-2008, 10:58 PM
Moderator
 
Join Date: Jul 2001
Location: southern California
Posts: 5,148
Default

Sorry, I don't use the http proxy on ASL.

I'm sure someone else could check.

Barry
__________________
http://DealBert.net
Home & business end-user since v1.x
  • ASL 6.3x, HP DL145 Dual Opteron, 1GB RAM, 6 gigE NICs, 50-IP Platinum License
  • ASL 7.3x, Dell PE1550 Dual PIII 1GHz, 1GB RAM, 2 NICs, 50-IP Platinum License
  • ASL 7.5x, 17-watt fanless mini-ITX system: MSI IM-945GSE-A Atom n270, 2GB RAM, Morex T3310 case. 2 Intel GigE, 3 VLANs. 80G 5200rpm 2.5" HD
    Netgear GS108T gigE VLAN switch & Linksys WRT54G WAP
    Total network infrastructure: 27 watts. 100-IP Home User. FiOS 10mb/2mb
Reply With Quote
  #5 (permalink)  
Old 07-29-2008, 02:12 AM
Wizard
 
Join Date: May 2003
Location: Brunswick, Maryland, USA
Posts: 2,667
Default

Quote:
Originally Posted by Billybob View Post
/dev/disk/by-label/storage
75G 480M 74G 1% /var/storage

So no problem for space. Buth du -ch |grep total of /var/chroot-http/var/cache directory still yields 17M

Could you check your cache directory and see what the size is?
Thanks Barry
Astaro went to a proprietary proxy with 7.x. Unfortunately this means we have no way to tweak it. Astaro has a firm predilection to use ram for caching. They'll push the machine to swap before they'll shift caching to disk. I would not htink your cache is going to get much bigger if your traffic patterns stay the way they are. Also keep in mind much more web traffic is generated on the fly and therefore isn't cachable.
__________________
50 user home license:ASL 7.5x p-4 celey 2.53 2 gigs ram 80 gig hdd intel/3com nics
50 user home license:ASL 7.5x p-4 xeon 2.8 ghz HT, 2 gigs ram, 250 gig HDD, 2 x Intel gig-e, 3com 3c905B

Registered Microsoft Partner
Emmanuel Computer Consulting, L.L.C.
http://www.emmanuelcomputerconsulting.com
Reply With Quote
  #6 (permalink)  
Old 07-29-2008, 06:40 AM
svens's Avatar
Senior Member
 
Join Date: Nov 2005
Posts: 260
Default

Hi
Quote:
Originally Posted by Billybob View Post
Recently upgraded from astaro 6.xx to 7.21. Hardware P4 2GHZ core duo 250gb hdd, 2 gb ram.

I have been running fine for a while, logged into the console just to see how everything was running and noticed that the proxy cache is at 17M. Let the http proxy run for about a week and its still at 17M. Is this normal? In astaro 6.3x under var/chroot-squid the cache was a few hundered megs. Under 7.21 under var/chroot-http, the cache is only 17M, I guess by design. Was wondering if I am the only one seeing this
Unfortunately this is a embarassing bug i introduced with V7.200 of ASG: The maxcachesize setting in /var/chroot-http/etc/httpproxy.ini is interpreted as Bytes, instead of Megabytes. This issue should be fixed with 7.300 (and with the 7.300 Beta out now). The 17MB you're counting is mostly the space required for the cache directory layout.

Cheers,

Sven.
__________________
Sven Schnelle
Software Architect
Astaro AG
Reply With Quote
  #7 (permalink)  
Old 07-29-2008, 06:44 AM
svens's Avatar
Senior Member
 
Join Date: Nov 2005
Posts: 260
Default

Hi,

Quote:
Originally Posted by William View Post
Astaro went to a proprietary proxy with 7.x. Unfortunately this means we have no way to tweak it. Astaro has a firm predilection to use ram for caching. They'll push the machine to swap before they'll shift caching to disk. I would not htink your cache is going to get much bigger if your traffic patterns stay the way they are. Also keep in mind much more web traffic is generated on the fly and therefore isn't cachable.
The HTTP Proxy doesn't cache web content in RAM - this is all done on disk. The only thing kept in RAM are:

- Categorization results
- DNS
- Cache index
and various other data structures

I've never seen an HTTP Proxy (> V7.200) causing the ASG to swap. If you have a box where the proxy eats all memory, send me a login (sschnelle@astaro.com).
I'm always interested in catching Bugs

Cheers,

Sven.
__________________
Sven Schnelle
Software Architect
Astaro AG
Reply With Quote
  #8 (permalink)  
Old 07-29-2008, 06:09 PM
Billybob's Avatar
Wizard
 
Join Date: Jul 2006
Location: United States
Posts: 637
Default

Quote:
Originally Posted by William View Post
Astaro went to a proprietary proxy with 7.x. Unfortunately this means we have no way to tweak it.
Yes, I read about that and find it a little faster than squid for general surfing purposes. By the way I followed your tweaking guide at Astaro's excessive swap usage and had my 6.xx system tweaked fairly nicely. Specially the echo 0 > /proc/sys/vm/swappiness part that I didn't think about using on my own.

Thanks sven for the explanation. I knew it had to be in the coding somewhere and glad that it will be fixed in the future. I guess I am old fashioned and like caching stuff even with fatter pipes to the internet at cheap prices.

Last edited by Billybob; 07-29-2008 at 06:33 PM.
Reply With Quote
  #9 (permalink)  
Old 07-29-2008, 06:59 PM
Wizard
 
Join Date: May 2003
Location: Brunswick, Maryland, USA
Posts: 2,667
Default

Quote:
Originally Posted by svens View Post
Hi,



The HTTP Proxy doesn't cache web content in RAM - this is all done on disk. The only thing kept in RAM are:

- Categorization results
- DNS
- Cache index
and various other data structures

I've never seen an HTTP Proxy (> V7.200) causing the ASG to swap. If you have a box where the proxy eats all memory, send me a login (sschnelle@astaro.com).
I'm always interested in catching Bugs

Cheers,

Sven.
I have posted about this on multiple occasions. Astaro's base squid and memory configurations pushed many machines into swap. I posted my tweaks for combating this. Astaro's excessive swap usage

squid by default(and therefore Astaro's base squid config) caches mostly to ram. That combined with a high base swappiness setting caused many 5-early 7.x machines to heavily swap. It's a proven tweak to a proven issue over a wide range of Astaro products.
__________________
50 user home license:ASL 7.5x p-4 celey 2.53 2 gigs ram 80 gig hdd intel/3com nics
50 user home license:ASL 7.5x p-4 xeon 2.8 ghz HT, 2 gigs ram, 250 gig HDD, 2 x Intel gig-e, 3com 3c905B

Registered Microsoft Partner
Emmanuel Computer Consulting, L.L.C.
http://www.emmanuelcomputerconsulting.com
Reply With Quote
  #10 (permalink)  
Old 07-29-2008, 08:29 PM
svens's Avatar
Senior Member
 
Join Date: Nov 2005
Posts: 260
Default

Hi William
,
Quote:
Originally Posted by William View Post
I have posted about this on multiple occasions. Astaro's base squid and memory configurations pushed many machines into swap. I posted my tweaks for combating this. Astaro's excessive swap usage

squid by default(and therefore Astaro's base squid config) caches mostly to ram. That combined with a high base swappiness setting caused many 5-early 7.x machines to heavily swap. It's a proven tweak to a proven issue over a wide range of Astaro products.
sorry, maybe i didn't made myself clear - i was talking explicitly about ASG V 7.200 and above, which doesn't use squid any longer, and the overall memory
usage of the HTTP Proxy should be *much* better then the versions before 7.100.

Cheers,

Sven.
__________________
Sven Schnelle
Software Architect
Astaro AG
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 02:40 AM.

 

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.


These pages are specifically maintained for the discussion of firewall issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases. issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases.