Is anyone out there running the Mikrotik web proxy under heavy load? How is it performing? We are seeing very heavy CPU load and web surfing seems to slow down at peak times. This is through a 3mbps pipe with quite a few dialup and wireless users.

Matt

I have the webproxy on 8mbps leased line. I have Intel Mother 1.8 with 512mb ram.
I don't have any problem...it is very fast. I have 400 customers connected with the router.
The CPU load is about 60 percent
Regards
M.

P4 1.8Ghz, 1Gigabyte RAM on Supermicro motherboard. Serves about 200 wireless users and 69 dialup lines. Cache is capped at 15Gigabyte.

http://www.fileholder.net/gateway/

Also manages p2p queues and many firewall rules. The moment I shutdown the web cache DST-NAT rule CPU usage drops to virtually nothing though. I figure it has something to do with seek time on the single IDE drive so at 8ms the most you can do is 100 requests a second. But if its not affecting you I dunno.

I have a 2.6Ghz P4 CPU ordered which is the fastest the motherboard will handle. Will see if that helps. Also, anxiously waiting for a 2.9RC release so I can see if that improves things.

Also, does ebay.com seem slow to anyone else?

Matt

Can you post that DST_NAT rule?

I have the webproxy on 8mbps leased line. I have Intel Mother 1.8 with 512mb ram.
I don't have any problem...it is very fast. I have 400 customers connected with the router.
The CPU load is about 60 percent
Regards
M.

What do you have your maximum object size at? What is the size of your cache?

Can you post that DST_NAT rule?

add in-interface=local dst-address=:80 protocol=tcp action=redirect to-dst-port=7080 comment="Redirect all port 80 to \
Squid" disabled=no

Matthew

if you can sacrifice with another installation for mikrotik and configure it as only web-proxy for users ... so the 1st mikrotik will be transparent for the new mikrotik ... I think this solution would help u n solve u the problem for many reasons .. 1st not all the rules { firewall, nating ... } applied on same server ... you don't need to configure the proxy settings at the client side ...and you will have both caching on 1st n 2nd MT