sön 2010-06-27 klockan 00:37 -0500 skrev Luis Daniel Lucio Quiroz:
You may also use siege a http stressing tool that supports also proxy,
siege has a bug so dont use it with digest-auth or ntlm auth, but basic auth
works very well
From what I can tell that's just an URL replayer?
such
Hi all,
I'm currently getting my squid working on a 2 Mb bandwidth plan that's serving
20 users. it's all good though our need for speed is increasing by the day.
soon enough i'll be serving up to 60 user, hence the need to get higher
bandwidth though here where the problem is.
as i'm using
No need to complicate matters that much. A single server (real or
virtual) with a single Squid will do fine.
You don't really need two nicks, but if the ISP are using DHCP for
address assignment then it helps (VLAN interfaces is sufficient
however). If static IP is used then connect both modems
sön 2010-06-27 klockan 14:33 +0300 skrev Roland RoLaNd:
What i understood:
1. i could set two distinct IPs on my nic (primary/secondary) using the cisco
router i route Primary to the first ISP and secondary to the second ISP.
2. all my users, use the same proxy 192.168.7.2:80
3. in
Le dimanche 27 juin 2010 02:51:38, Henrik Nordström a écrit :
sön 2010-06-27 klockan 00:37 -0500 skrev Luis Daniel Lucio Quiroz:
You may also use siege a http stressing tool that supports also proxy,
siege has a bug so dont use it with digest-auth or ntlm auth, but basic
auth works very
sön 2010-06-27 klockan 10:07 -0500 skrev Luis Daniel Lucio Quiroz:
Yes, but when it finishes, it gives you statistical information about response
Yes, but of what value if you don't know what it means or what was
actually tested?
Regards
Henrik
