Three strategies are employed to test the performance of the system. The first involves tracking the number of input digits required to obtain each output digit. The second is to use the Glasgow Haskell compilers profiling tool to discover which operations are contributing to the time and memory usage. The third is to simply find suitably complex operations and time them approximately to give a `feel' for the overall performance of the system.