Re: Bad performance

You are forgetting that apache runs in user space, and tux is in kernel
space - so nfs can present dirrent problems to apache and tux.

and 2.2.7 is only the version of the user-space utilities. If you are using
a kernel from some distro, you can find the version by looking at it's
source,

on my machine it's at
 /usr/src/linux-2.4/include/net/tux_u.h ,

the first few lines will tell you the version, like this

#define TUX_MAJOR_VERSION               2
#define TUX_MINOR_VERSION               1
#define TUX_PATCHLEVEL_VERSION          1

this means tux 2.1.1



----- Original Message -----
From: "Kees Hoekzema" <[email protected]>
To: <[email protected]>
Sent: Saturday, October 05, 2002 10:18 PM
Subject: RE: Bad performance


> currently i'm running tux-2.2.7
>
> NFS can't be the problem. My apache server can serve the same file with
more
> than 1000 req/s (still slow, but ok, it is a loaded server ;))
>
> Also I noticed that the peformance decreases in time. When freshly started
> tux can do a lot more than the 3 r/s (more than 10.000 when the server is
> idle actually).
>
> It could be an NFS bug in 2.4.18 which has bugged me before. I'm now
> patching 2.4.19 with tux, hopefully that solves the poblem :)
>
> -kees
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On
Behalf
> Of Alex Kramarov
> Sent: Saturday, October 05, 2002 10:50 PM
> To: [email protected]
> Subject: Re: Bad performance
>
>
> first i would do the benchmark while serving from local hd and see if that
> solves the problem.
>
> That is the exact tux version you are running ?
> ----- Original Message -----
> From: "Kees Hoekzema" <[email protected]>
> To: <[email protected]>
> Sent: Saturday, October 05, 2002 9:10 PM
> Subject: Bad performance
>
>
> > Hello list,
> >
> > I'm running a Tux 2.0 server, under a high load. The server is a dual
> Athlon
> > 1400MP w/ 1G ram and serving the files from NFS. The loadaverages are
> around
> > 4.
> >
> > When I benchmark this server it is able to almost 3.24 [requests/sec].
> > On the server Tux is eating up almost all the CPU:
> > USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
> > #-1        754 93.3  0.0  1612  700 ?        R    Oct04 1308:59 [TUX
> worker
> > 0]
> >
> > My startup script configures tux:
> >
> >     echo "Starting tux:"
> >     ## tux configuratie:
> >     echo "1" > /proc/sys/net/tux/threads
> >     echo "0" > /proc/sys/net/tux/compression
> >     echo "/mnt/web/tux" > /proc/sys/net/tux/documentroot
> >     echo "nobody" > /proc/sys/net/tux/cgi_uid
> >     echo "nobody" > /proc/sys/net/tux/cgi_gid
> >     echo "1" > /proc/sys/net/tux/virtual_server
> >     echo "10" > /proc/sys/net/tux/keepalive_timeout
> >     echo "0" > /proc/sys/net/tux/logging
> >     echo "1" > /proc/sys/net/tux/generate_cache_control
> >     echo "/www/logs/tux" > /proc/sys/net/tux/logfile
> >     echo "tweakers.net" > /proc/sys/net/tux/default_vhost
> >     echo "http://0.0.0.0:8080" > /proc/net/tux/0/listen/0
> >     echo "8080" > /proc/sys/net/tux/clientport
> >     echo "10" > /proc/sys/net/tux/keepalive_timeout
> >     echo "20000" > /proc/sys/net/tux/max_connect
> >     echo "10000" > /proc/sys/net/tux/max_keepalives
> >
> >     ## tux starten:
> >     /usr/sbin/tux --daemon --threads 1 --docroot /www/tux
> >
> > I can't figure out where the problem is, I hope someone can help me.
> >
> > tia,
> > Kees Hoekzema
> >
> >
> >
> > _______________________________________________
> > tux-list mailing list
> > [email protected]
> > https://listman.redhat.com/mailman/listinfo/tux-list
> >
>
>
>
> _______________________________________________
> tux-list mailing list
> [email protected]
> https://listman.redhat.com/mailman/listinfo/tux-list
>
>
>
> _______________________________________________
> tux-list mailing list
> [email protected]
> https://listman.redhat.com/mailman/listinfo/tux-list
>