Have you tried profiling the code? Also I would have thought that with files that size a lot of memory would be required, which might lead to a lot of page swapping. So I would look at options that reduce memory usage. If that is the problem the profiling might be rather misleading. So getting some low level performance data on your machine during the course of its run could be useful. Also does the package itself have any verbose logging options with timestamps?