1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Nel] NeL Network Engine</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:lecroart%40nevrax.com">
<LINK REL="Previous" HREF="000287.html">
<LINK REL="Next" HREF="000291.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Nel] NeL Network Engine</H1>
<B>Vianney Lecroart</B>
<A HREF="mailto:lecroart%40nevrax.com"
TITLE="[Nel] NeL Network Engine">lecroart@nevrax.com</A><BR>
<I>Wed, 28 Feb 2001 10:07:19 +0100</I>
<P><UL>
<LI> Previous message: <A HREF="000287.html">[Nel] NeL Network Engine</A></li>
<LI> Next message: <A HREF="000291.html">[Nel] NeL Network Engine</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#289">[ date ]</a>
<a href="thread.html#289">[ thread ]</a>
<a href="subject.html#289">[ subject ]</a>
<a href="author.html#289">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hello,
In fact, we don't want to know the theorical limit. we know that we can
change this value in the kernel sources and recompile it.
What we don't know is the thread number limit after what the system uses too
much CPU. In the linuxthread faq, they
said that an application should not create more than 100 thread. In this
case, we have to forget the solution where each
socket is on a thread and use a blocked receive(). The problem is that
select() is quite slow and if we have only 100 thread,
each thread needs to manage, with a select(), around 50 players and we ll
lost lot of time to create the array for the select()
and check who have wakeup the select().
Vianney Lecroart
---
lead network programmer / nevrax.com
icq#: 6870415
homepage: <A HREF="http://ace.planet-d.net">http://ace.planet-d.net</A>
www.geekcode.com: GCS/E d- s+++: a-- C+++$ UL++ P- L+++>+$ E+>- W++ N+ o? K-
w++$ O- M- V- PS- PE? Y PGP t 5? X+ R- tv++ b- DI D+ G e++ h+ r-- y?
----- Original Message -----
From: "Thierry Mallard" <<A HREF="mailto:thierry@mallard.com">thierry@mallard.com</A>>
To: <<A HREF="mailto:nel@nevrax.org">nel@nevrax.org</A>>
Sent: Wednesday, February 28, 2001 8:31 AM
Subject: Re: [Nel] NeL Network Engine
><i> On Mon, Feb 26, 2001 at 05:49:39PM +0100, Bernard Hugueney wrote:
</I>><i> > [ Linux and threads ]
</I>><i> > Well, I'm as far as possible from a threads expert, but I think that
</I>><i> > what makes LinuxThreads special is that they are system threads (vs user
</I>><i> > threads) maybe heavier, but making use of SMP, so basically, I think
</I>><i> > the max nb of threads is very much system dependand (SMP?).
</I>><i>
</I>><i> In Linux 2.4.x, you may configure the maximum threads with
</I>><i> /proc/sys/kernel/threads-max, if i remember correctly.
</I>><i>
</I>><i> But the default value (4096) is still much more that what the default
</I>kernel
><i> can really handle nicely, as is it said in some other posts. We'll have to
</I>><i> look deeper into this...
</I>><i>
</I>><i>
</I>><i> Shaman
</I>><i>
</I>><i> --
</I>><i> Thierry Mallard |
</I>><i> GnuPG key on wwwkeys.pgp.net |
</I>><i> key 0xA3D021CB |
</I>><i> <A HREF="http://thierry.mallard.com">http://thierry.mallard.com</A> |
</I>><i>
</I>><i> _______________________________________________
</I>><i> Nel mailing list
</I>><i> <A HREF="mailto:Nel@nevrax.org">Nel@nevrax.org</A>
</I>><i> <A HREF="/mailman/listinfo.cgi/nel">/mailman/listinfo.cgi/nel</A>
</I>
</pre>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI> Previous message: <A HREF="000287.html">[Nel] NeL Network Engine</A></li>
<LI> Next message: <A HREF="000291.html">[Nel] NeL Network Engine</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#289">[ date ]</a>
<a href="thread.html#289">[ thread ]</a>
<a href="subject.html#289">[ subject ]</a>
<a href="author.html#289">[ author ]</a>
</LI>
</UL>
</body></html>
|
