There's a discussion of those page faults from early in the Beta testing of SaH v7, http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=1831&postid=40514 (http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=1831&postid=40514) is the first post on that issue. But the short version is that it is FFTW's implementation of the type 2 DCT which is doing that. It seems to be about 128 per DCT, suggesting they have to allocate an extra 512 KB of RAM as scratch memory for each DCT. Because we're doing 519336 of those in each WU, it would certainly be nice if we could allocate a permanent array for the purpose and tell FFTW about it, but that feature isn't available.
I've been watching for an optimized open source DCT we could substitute, but haven't yet found one.
Joe
OK, since it is known I won't worry about it anymore.
Thanks for the quick reply.