--
Neil Bothwick
Drink varnish and you'll have a lovely finish.
Mileage1709.xlsx
Description: MS-Excel 2007 spreadsheet
pgp1vHCBOVFok.pgp
Description: OpenPGP digital signature
practical way to solve this sort of problem?
Use a reverse proxy in caching mode.
A request served up by the proxy server is a request not served up by
Apache.
Squid, nginx and varnish are all decent for the purpose, though squid
and nginx are probably the more polished than varnish
On Sun, 1 May 2005 17:31:32 +0200, Lubos Kolouch wrote:
how to convince liborbit not to use i386- ?
Have you changed CHOST in /etc/make.conf?
--
Neil Bothwick
Drink varnish and you'll have a lovely finish.
pgpzdcZvlVaLn.pgp
Description: PGP signature
of problem?
Use a reverse proxy in caching mode.
A request served up by the proxy server is a request not served up by
Apache.
Squid, nginx and varnish are all decent for the purpose, though squid
and nginx are probably the more polished than varnish.
Thanks Michael, I think I will set up nginx
in /etc/make.conf?
--
Neil Bothwick
Drink varnish and you'll have a lovely finish.
--
gentoo-user@gentoo.org mailing list
Drink varnish and you'll have a lovely finish.
signature.asc
Description: PGP signature
see the man page.
--
Neil Bothwick
Drink varnish and you'll have a lovely finish.
pgp7z8gnZ6w4g.pgp
Description: OpenPGP digital signature
, etc. The dom0 role has 15 tasks including monitoring, xen, grub.
The domU role basically just configures rc.conf.
An actual web server with apache/php has just about 20 tasks. A
load-balancer
with varnish/nginx/keepalived has just about the same. A database has
about
30 tasks because it also
disk
between /, /home swap as you see fit.
--
Neil Bothwick
Drink varnish and you'll have a lovely finish.
pgpzElG0x3awt.pgp
Description: OpenPGP digital signature
James wrote:
So the best I can do is forward all traffic( 80, 443, etc) for the
group of websites to a proxy behind the firewall, then use software
such as what kashani suggested (proxypass, Squid, ngnix,
lighttpd, or Varnish) and parse the traffic with some form of
vhosts implementation
MaxClients. Is a RAM upgrade the only
practical way to solve this sort of problem?
Use a reverse proxy in caching mode.
A request served up by the proxy server is a request not served up by
Apache.
Squid, nginx and varnish are all decent for the purpose, though squid
and nginx
practical way to solve this sort of problem?
Use a reverse proxy in caching mode.
A request served up by the proxy server is a request not served up by
Apache.
Squid, nginx and varnish are all decent for the purpose, though squid
and nginx are probably the more polished than varnish.
Thanks
roxy/haproxy-1.5.14
sys-apps/flashrom-0.9.6.1
sys-apps/flashrom-0.9.7
sys-process/htop-1.0.3
sys-process/incron-0.5.10
sys-process/incron-0.5.10-r1
www-apache/mod_perl-2.0.8
www-apache/mod_perl-2.0.10_pre201601
www-servers/varnish-3.0.7
www-servers/varnish-4.0.3
and configures additional stuff like postfix,
nrpe, etc. The dom0 role has 15 tasks including monitoring, xen, grub.
The domU role basically just configures rc.conf.
An actual web server with apache/php has just about 20 tasks. A
load-balancer
with varnish/nginx/keepalived has just about the same
a lot, about the only distro I never look at is
Gentoo - blame me for the low ranking if you like :)
--
Neil Bothwick
Drink varnish and you'll have a lovely finish.
pgp3Q5khWtJxE.pgp
Description: OpenPGP digital signature
0
read_all = false
delete = true
--
Neil Bothwick
Drink varnish and you'll have a lovely finish.
pgpn587UHp8Y7.pgp
Description: OpenPGP digital signature
, and now I find myself
periodically up against MaxClients. Is a RAM upgrade the only
practical way to solve this sort of problem?
Use a reverse proxy in caching mode.
A request served up by the proxy server is a request not served up by
Apache.
Squid, nginx and varnish are all decent
, nginx and varnish are all decent for the purpose, though squid
and nginx are probably the more polished than varnish.
Grant,
If you optimized the site well, I would imagine your RAM needs per page
request would go down and you could possibly increase MaxClients again.
Have you given it a try
is a request not served up by
Apache.
Squid, nginx and varnish are all decent for the purpose, though squid
and nginx are probably the more polished than varnish.
Grant,
If you optimized the site well, I would imagine your RAM needs per page
request would go down and you could possibly
most powerful and flexible option, ngnix,
lighttpd, or Varnish.
There are some security concerns with this type of setup, ie running
daemons open to the public on your firewall, reverse proxies need to be
locked down, hard to do IP based restrictions on the webserver, etc.
kashani
the best I can do is forward all traffic( 80, 443, etc) for the
group of websites to a proxy behind the firewall, then use software
such as what kashani suggested (proxypass, Squid, ngnix,
lighttpd, or Varnish) and parse the traffic with some form of
vhosts implementation on a single server (nated IP
On 24 Sep 2009, at 16:30, James wrote:
...
So the best I can do is forward all traffic( 80, 443, etc) for the
group of websites to a proxy behind the firewall, then use software
such as what kashani suggested (proxypass, Squid, ngnix,
lighttpd, or Varnish) and parse the traffic with some form
es, which were manufactured proud. Hardcore
> O/C's flatten the CPU too, but I'd avoid anything as radical because it can
> go
> badly wrong if you remove more than the surface varnish from the chip.
>
> In the interim, opening the side panel may also help in hot weather.
>
> --
> Regards,
> Mick
I'd avoid anything as radical because it can go
badly wrong if you remove more than the surface varnish from the chip.
In the interim, opening the side panel may also help in hot weather.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
.
A request served up by the proxy server is a request not served up by
Apache.
Squid, nginx and varnish are all decent for the purpose, though squid
and nginx are probably the more polished than varnish.
Grant,
If you optimized the site well, I would imagine your RAM needs per page
contact
> with the CPU. I've seen 15°C improvement in a Zalman CPU cooler after excess
> metal was removed from copper pipes, which were manufactured proud. Hardcore
> O/C's flatten the CPU too, but I'd avoid anything as radical because it can go
> badly wrong if you remove more than th
ks are poorly manufactured and require flattening with
>> wet 'n dry sandpaper to get a flat enough surface and improve their contact
>> with the CPU. I've seen 15°C improvement in a Zalman CPU cooler after excess
>> metal was removed from copper pipes, which were manufactured proud
nufactured and require flattening with
>> wet 'n dry sandpaper to get a flat enough surface and improve their contact
>> with the CPU. I've seen 15°C improvement in a Zalman CPU cooler after excess
>> metal was removed from copper pipes, which were manufactured proud. Hardcore
gt; > after excess metal was removed from copper pipes, which were manufactured
> > proud. Hardcore O/C's flatten the CPU too, but I'd avoid anything as
> > radical because it can go badly wrong if you remove more than the surface
> > varnish from the chip.
> >
> >
'. * Worf
Neil Bothwick
Deliver a pizza? Whoever heard of a liver pizza?
Neil Bothwick
Those who live by the sword get shot by those who don't.
Neil Bothwick
Drink varnish and you'll have a lovely finish.
Neil Bothwick
I am Superconductor Borg, assimilation resistance is futile.
Neil Bothwick
30 matches
Mail list logo
