> > That's odd. This test only takes a few seconds on an amd64 system. Do > > you have any local changes to libc, or any particular /etc/malloc.conf > > settings, which could explain the slowdown? > > Ahh you caught me. Yes, I had /etc/malloc.conf settings. I'll try it > again without those settings. I was running it on amd64. Thanks!
What flags were you using? As its name implies, this test causes a lot of memory to be allocated, so malloc flags such as F and G will take a toll... > I think that was the cause of the kqueue hang I was seeing. I launched > the regression tests and came back hours later and they were still > "running". All CPU cores were at 100% idle and it said it was still > running kqueue. I just ran it on this i386 snapshot without any malloc.conf > settings and it ran quickly. ... but they should not cause the system to be idle nevertheless. So this is worth investigating.
