Messages in this thread | | | Subject | Re: Painfully slow exec() | Date | Fri, 18 Sep 1998 13:22:54 +0200 | From | Olaf Titz <> |
| |
> didn't make any difference. It's most probably inn-2.1's fault, but I > think the issue is worth investigating a little further. >... > strace output shows that it's the exec() syscall itself that's taking an > unusual amount of time -- between 10 and 50 seconds! While this is > happening, ps -axl shows the process doing the exec() as > > 100040 6 15998 30053 7 4 0 0 wait_on_buf DWN ? 0:00 > \_/usr/local/news/bin/innd -p7 > > and, what's more weird, vmstat 1 shows "lots" of blocks being written to > the disk, a lot more than usual:
innd has the whole history dbz file mmaped, and that is huge. Perhaps, because it is R/W and close-on-exec, what your system does is trying to sync that in some way.
Standard advice: try --enable-tagged-hash for INN, that needs _much_ less memory.
CCd to the INN list: is that in some way a known issue?
olaf
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |