m (Heading levels as per wiki standards)
|(One intermediate revision by one user not shown)|
Latest revision as of 15:31, 5 April 2007
|Haskell Performance Resource|
 1 Improving performance for FFI code
 1.1 Use "unsafe" foreign imports
If you annotate a foreign import declaration with the unsafe keyword, this indicates to the compiler that (1) the call will not invoke another Haskell function, directly or indirectly, and (2) you don't mind if any other running Haskell threads in the system are blocked for the duration of the call.
These restrictions enable the compiler to generate a much more efficient call. In particular, GHC will generate a simple inline function call for an unsafe call, but a safe call by contrast is quite heavyweight: it involves saving some state on the Haskell stack, and a couple of calls into the runtime are made in addition to the foreign call itself.
 1.2 Take care when marshalling
One big performance eater can be marshalling from foreign code to local code. Try to do as little of it as possible, that is, try to keep your data on one side of the FFI. If you do need to marshal data across the FFI, do it in large chunks; calling across the FFI to generate datastructures is much more expensive than building appropriate structures in Haskell and then handing those off in one go.