One thing I've noticed is that the default config seems to overload on lower
end CPU's. The 4 machines I've installed(750 Duron, 1g athlon, 2xPIII750,
4xPIIXEON450) all QR about 80% of the requests. If I drop the max
connections to 256 and increase the threads to 300 I only QR about 20% of
the time and the machines don't run at 100% processor. However most of the
nodes I talk to are QRing me about 40-60% of the time still. It seems like
with the current defaults it uses more resources QRing than processing
searches. I've fixed my node but probably 80% of normal users don't even
look at the config file or would have any idea how to tweak it. Defaults
should not assume that the users have the latest and greatest hardware.

Dave

----- Original Message ----- 
From: "Ian Clarke" <[EMAIL PROTECTED]>
To: "Discussion of development issues" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Friday, October 31, 2003 7:37 AM
Subject: [freenet-dev] Usability improvement ideas


> As the developers work hard to improve the core operation of Freenet, it
> can be easy to forget about the more superficial, but equally important
> aspects of Freenet, namely installation procedures, and usability for
> newbies.
>
> For those intimately familiar with Freenet's operation it can be
> difficult to look at Freenet's operation from the perspective of someone
> new to the software, and often something that seems minor and trivial to
> a core developer, might have a significant impact on a new user's view
> of the software.
>
> So, this email is an invitation to anyone that has constructive
> criticism or suggestion's for how Freenet's "first impression" can be
> enhanced.  Topics include installation, FProxy, even the website's layout.
>
> Ian.
>
> _______________________________________________
> Devl mailing list
> [EMAIL PROTECTED]
> http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
>

_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl

Reply via email to