When logging into kde on our school lan, sometimes we are left with a blank screen which goes no further after eg. the flashing globe icon. This only happens if we all login together at the start of the lesson. If we wait a while and login one at a time before the next person logs in, then it's OK. It seems as if there is too much demand on the nfs server at peak times. I've tried all the sync, async and rsize=8192 type of tricks. This may also be linked to another post I made about slow nis logins. Any ideas anyone? All 9.0 lan with 10/100 switches all at 100. Thanks, Steve.
On Wednesday 14 January 2004 18:51 pm, steve-ss wrote:
When logging into kde on our school lan, sometimes we are left with a blank screen which goes no further after eg. the flashing globe icon. This only happens if we all login together at the start of the lesson. If we wait a while and login one at a time before the next person logs in, then it's OK. It seems as if there is too much demand on the nfs server at peak times. I've tried all the sync, async and rsize=8192 type of tricks. This may also be linked to another post I made about slow nis logins. Any ideas anyone? All 9.0 lan with 10/100 switches all at 100.
Just how many people are logging in simultaneously? What are the specs of the server? Dylan
Thanks, Steve.
-- "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Benjamin Franklin
On Wednesday 14 January 2004 19:12, Dylan wrote:
On Wednesday 14 January 2004 18:51 pm, steve-ss wrote:
When logging into kde on our school lan, sometimes we are left with a blank screen which goes no further after eg. the flashing globe icon. This only happens if we all login together at the start of the lesson. If we wait a while and login one at a time before the next person logs in, then it's OK. It seems as if there is too much demand on the nfs server at peak times. I've tried all the sync, async and rsize=8192 type of tricks. This may also be linked to another post I made about slow nis logins. Any ideas anyone? All 9.0 lan with 10/100 switches all at 100.
Just how many people are logging in simultaneously? What are the specs of the server?
20 logins simultaneously. PIV 2.4 with 1024Mb ram and 80Gb ide disk Steve.
On Wednesday 14 January 2004 20:22 pm, steve-ss wrote:
On Wednesday 14 January 2004 19:12, Dylan wrote:
On Wednesday 14 January 2004 18:51 pm, steve-ss wrote:
When logging into kde on our school lan, sometimes we are left with a blank screen which goes no further after eg. the flashing globe icon. This only happens if we all login together at the start of the lesson. If we wait a while and login one at a time before the next person logs in, then it's OK. It seems as if there is too much demand on the nfs server at peak times. I've tried all the sync, async and rsize=8192 type of tricks. This may also be linked to another post I made about slow nis logins. Any ideas anyone? All 9.0 lan with 10/100 switches all at 100.
Just how many people are logging in simultaneously? What are the specs of the server?
20 logins simultaneously. PIV 2.4 with 1024Mb ram and 80Gb ide disk
Yes, that'd be plenty to handle that... (IMHO) Fair enough... how is the exports, fstab and autofs (if you are using it) configured? Dylan
Steve.
-- "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Benjamin Franklin
steve-ss
It seems as if there is too much demand on the nfs server at peak times.
Try to export some filesystems as read-only (/home must be rw). This will decrease the disk load on the server since for instance a command's atime is not modified when the command is started by an NFS client. Also use some performance monitors to see where the bottleneck is. -- A.M.
On Thursday 15 January 2004 15:02, Alexandr Malusek wrote:
steve-ss
writes: It seems as if there is too much demand on the nfs server at peak times.
Try to export some filesystems as read-only (/home must be rw). This will decrease the disk load on the server since for instance a command's atime is not modified when the command is started by an NFS client.
Also use some performance monitors
Any recommendations? What should I be looking for? Thanks, Steve.
steve-ss
On Thursday 15 January 2004 15:02, Alexandr Malusek wrote:
steve-ss
writes: It seems as if there is too much demand on the nfs server at peak times.
Also use some performance monitors
Any recommendations? What should I be looking for?
If there are no HW problems with the network (I suppose it is a 100 Mbps or faster network) then the disk is often the bottleneck. Measure the disk performance, especially random access reads and writes. A disk with 10 ms average seek time can, on average, perform 100 random IO operations per second. It corresponds to 800 KiB/s of transfered data for 8 KiB blocks. This may not be enough for 20 clients. You can measure the server performance by "iostat -x" . Use bonnie or bonnie++ to see how the iostat numbers change with the disk access pattern. -- A.M.
participants (3)
-
Alexandr Malusek
-
Dylan
-
steve-ss