On Wed, Nov 10, 2004 at 10:07:46AM +, Malcolm Wallace wrote:
Simon Marlow [EMAIL PROTECTED] writes:
On 09 November 2004 17:04, Duncan Coutts wrote:
Are you using BinMem, or BinIO?
BinIO
Ah. BinIO is going to be a lot slower than BinMem, because it does
an hPutChar
On 09 November 2004 17:04, Duncan Coutts wrote:
Are you using BinMem, or BinIO?
BinIO
Ah. BinIO is going to be a lot slower than BinMem, because it does
an hPutChar for each character, whereas BinMem just writes into an
array. I never really optimised the BinIO path, because we use
Duncan Coutts [EMAIL PROTECTED] writes:
I'm looking for some advice on profiling and any suggestion on what
might be going on with this program.
One suggestion might be to serialise (key,value) pairs to file as
they are first encountered, rather than waiting until they are all
inside
On 09 November 2004 12:54, Duncan Coutts wrote:
[snip]
When I do time profiling, the big cost centres come up as putByte and
putWord. When I profile for space it shows the large FiniteMaps
dominating most everything else. I originally guessed from that that
the serialisation must be forcing
On Tue, 2004-11-09 at 14:45, Simon Marlow wrote:
On 09 November 2004 12:54, Duncan Coutts wrote:
[snip]
When I do time profiling, the big cost centres come up as putByte and
putWord. When I profile for space it shows the large FiniteMaps
dominating most everything else. I originally
