Hey folks,
Now that I want to install this in production, I have to ask about dsktune :-)
Some of what it is telling me just seems plain incorrect. Let''s have
a look
WARNING: There are only 1024 file descriptors (hard limit) available, which
limit the number of simultaneous connections.
WARNING: There are only 1024 file descriptors (soft limit) available, which
limit the number of simultaneous connections.
Yet :
[root@fileserver ~]# !cat
cat /proc/sys/fs/file-max
306460
I''m also wondering about whether or not this is really something to
worry about :
NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds
(120 minutes). This may cause temporary server congestion from lost
client connections.
I''ve got 20 or so users. Is this really an issue for me? Changing
it is of course pretty trivial, but I''d rather not if I do not have
to.
thanks,
-Alan
--
“Don''t eat anything you''ve ever seen advertised on TV”
- Michael Pollan, author of "In Defense of Food"
Alan McKay wrote:> Hey folks, > > Now that I want to install this in production, I have to ask about dsktune :-) > > Some of what it is telling me just seems plain incorrect. Let''s have a look > > WARNING: There are only 1024 file descriptors (hard limit) available, which > limit the number of simultaneous connections. > > WARNING: There are only 1024 file descriptors (soft limit) available, which > limit the number of simultaneous connections. > > Yet : > > [root@fileserver ~]# !cat > cat /proc/sys/fs/file-max > 306460 >What does ulimit -n say?> I''m also wondering about whether or not this is really something to > worry about : > NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds > (120 minutes). This may cause temporary server congestion from lost > client connections. > > I''ve got 20 or so users. Is this really an issue for me? Changing > it is of course pretty trivial, but I''d rather not if I do not have > to. >It''s probably not an issue if you have 20 users. It might be an issue if you have several thousand users.> thanks, > -Alan > > >
On Mon, Dec 7, 2009 at 10:15 AM, Rich Megginson <rmeggins@redhat.com> wrote:> What does > ulimit -n > say?Aha! [root@fileserver ~]# ulimit -n 1024> It''s probably not an issue if you have 20 users. It might be an issue if > you have several thousand users.OK, thanks. -- “Don''t eat anything you''ve ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"
> Aha! > > [root@fileserver ~]# ulimit -n > 1024So there is still no real description on why this matters. It is just mentioned in passing here : http://www.redhat.com/docs/manuals/dir-server/8.1/install/Installation_Guide-RHEL-Requirements.html#Installation_Guide-Platform_Support-File_Tuning with no detail. An no mention of ulimit. Ulimit is for the shell so I''m not sure why that matters for Centos-DS And with 20 some users, will this really matter to me? -- “Don''t eat anything you''ve ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"
Alan McKay wrote:>> Aha! >> >> [root@fileserver ~]# ulimit -n >> 1024 >> > > So there is still no real description on why this matters. It is just > mentioned in passing here : > http://www.redhat.com/docs/manuals/dir-server/8.1/install/Installation_Guide-RHEL-Requirements.html#Installation_Guide-Platform_Support-File_Tuning > with no detail. An no mention of ulimit. Ulimit is for the shell > so I''m not sure why that matters for Centos-DS >See http://directory.fedoraproject.org/wiki/Performance_Tuning#Linux> And with 20 some users, will this really matter to me? >No.