...:::[69]Team:::...(BINE AI VENIT)
Ne-am mutat pe www.update.dublu.ro
|
Nou pe simpatie:
Profil Lorena13
 | Femeie
24 ani
Bucuresti
cauta Barbat
26 - 40 ani |
|
|
...:::[69]Team:::...(BINE AI VENIT)ReguliInregistrareLoginPozeNu sunteti logat. Lista Forumurilor Pe Tematici
|
| #1 |
|
|
Sunt setari pt YnHub --am postat in Engleza pt ca este o limba comuna:
The following settings are optimized for squeezing in as many users as possible into the hub, without losing too much "functionality".
Since the userlimit is depending on the upload band-width of the server,
you can - with a few simple steps - increase the userlimit quite drastically.
On our testserver, a P2 400Mhz with 256 MB of PC100 on a 10Mbit full duplex connection we managed to reach 3800 users with these settings. With the default settings the hub barely (with a massive lag) managed to surpass 3000.
1) Work pace: A slow work pace can do wonders for the hub when the connection (upload) is maxed out. Try
"Skalman" (2), "Sleeping" (1) or even "Coma" (0).
(Settings > Hub Control > Work Pace)
2) DNS Lookup: Can slow the login procedure down quite a bit, you might want that disabled.
(Security > General security > uncheck "Perform DNS lookup"
3) Spam control: By limiting the MyINFO- and search-rate we can gain quite a few users.
Set "New MyINFOs" to "5 per 300 seconds". Make the checkbox "grayed".
Set "Searching" to "5 per 300 seconds". Make the checkbox "grayed".
Set "Mainchat" to "3-4 per 10 seconds". Use a normal check, not a "grayed" one.
Set "Private messages" to whatever you like. I use "5 per 10 seconds" and "grayed".
Set "Nicklist" to "2 per 600 seconds". Make the checkbox "grayed".
You can leave "Max spam warnings" untouched at 6, but I prefer 3.
(Security > Spam control)
4) Length restrictions: We can leave most of these settings to default, except for "Mainchat
max length". On a large hub a long message in the mainchat can do quite a bit of damage to your bandwidth.
Set "Mainchat max length" to 400 or less.
(Security > Restrictions > Length restrictions)
5) Passive search restrictions: This is a gem. We can save quite a bit of bandwidth here.
But we still want the hub to be "useable" for passive users,
so we can't go overboard in the restrictions.
I have found that the following settings seem to be a good compromise.
This is however kind of a delicate matter. Passive users may not like to be limited too much.
Use this feature wisely, and listen to what your users have to say.
Set "Max search replies" to between 50 and 100.
Set "Min length any file type" and "Min length specific file type" to whatever you like.
(Security > Restrictions > Passive search restrictions)
6) MyINFO distribution: This is probably where we have the most to gain, bandwidth wise.
On all of these settings we will use a "grayed" check, so that the operators get any (and all) changes instantly.
You can of course let the description tag be visible to all users if you like,
by unchecking "Disable description tag".
However, that will affect the bandwidth useage and thus the userlimit quite a bit.
Set "Pool MyINFO changes for" to 5 minutes and "grayed".
Set "Disable description" to "grayed".
Set "Disable description tag" to "grayed".
Set "Disable email" to "grayed".
Set "Disable connection speed information" to disabled (unchecked).
(Security > Restrictions > MyINFO distribution)
Simple as that. This SHOULD increase the usercount quite a bit if bandwidth is your limitation.
_______________________________________
[69]ceostoy*<cL>
|
|
| |
|
