John Wiegley <[email protected]> wrote: > I'm not sure whether this is a Privoxy issue, or an OpenIndiania issue. The > webpage in question is this particularly badly-behaved site: > > http://www.bestbeefjerky.org/2011/04/bacon-forever-smoky-original.html > > For whatever reason, this site will generate an endless stream of connections, > hammering Privoxy very hard. > > With the Privoxy 3.0.8 that you get from "pkg install privoxy", this site > causes no performance problems. Privoxy stays at <1% CPU. But when I build > 3.0.19 from source, it causes CPU utilization from Privoxy to climb into the > 50-60% range, and to stay there for several minutes, long after I quit my > browser. > > I turned on lots of debug output in the Privoxy log (connections, I/O, data), > and didn't see anything abnormal during this CPU spike. In fact, CPU was > holding at 42% while nothing additional was getting written to the log.
Can you reproduce the problem with the debug directives recommended at http://www.privoxy.org/user-manual/contact.html#CONTACT-BUGS and provide a link to the log file? > Switching to truss, I saw thousands and thousands of calls to lwp_pack and > lwp_unpack, over and over, which didn't stop until the CPU quieted down. Does http://config.privoxy.org/show-status show that FEATURE_PTHREAD is enabled? What does the CPU utilisation look like if you add "single-threaded" to Privoxy's configuration file? > Here is how I configured Privoxy for OI: > > ./configure --prefix=/usr --sysconfdir=/etc/privoxy --localstatedir=/var \ > CFLAGS='-O3 -pipe -fomit-frame-pointer -funroll-loops -ffast-math > -fno-exceptions' \ > --enable-compression --with-user=webservd --with-group=webservd > > Does this ring any bells for anyone? I'm back to using 3.0.8, but am curious > as to why I couldn't upgrade to 3.0.19. Are you using the same pcre version as with 3.0.8? Does it make a difference if you use the default CFLAGS? Can you reproduce the problem if you build 3.0.8 from source? While your configure line looks good in theory, Privoxy's autoconf mess hasn't been explicitly updated to deal with the various OpenSolaris forks. There are a couple of code paths written for ancient Solaris versions and it's possible that they either aren't enabled on your system or are enabled but shouldn't. Fabian ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
signature.asc
Description: PGP signature
