On Wed, Jan 9, 2013 at 11:38 PM, Joachim Breitner
m...@joachim-breitner.de wrote:
Am Mittwoch, den 09.01.2013, 15:11 +0100 schrieb Erik Hesselink:
We finally solved the problems by completely moving
to strict map operations, strict MVar/TVar operations, and strict data
types.
do you mean
On Tue, Jan 8, 2013 at 10:54 PM, Joachim Breitner
m...@joachim-breitner.de wrote:
Am Dienstag, den 08.01.2013, 13:01 -0800 schrieb Evan Laforge:
surprisingly, deepseq is not used as much as I thought.
http://packdeps.haskellers.com/reverse/deepseq lists a lot of packages,
but (after
Hi Erik,
Am Mittwoch, den 09.01.2013, 14:23 +0100 schrieb Erik Hesselink:
We've also used this approach to debug space-leaks, and would have
loved such a tool. We used deepseq, and compared the heap profiles. We
finally found the leaks this way, and fixed them using strictness
annotations.
On Wed, Jan 9, 2013 at 2:40 PM, Joachim Breitner
m...@joachim-breitner.de wrote:
Hi Erik,
Am Mittwoch, den 09.01.2013, 14:23 +0100 schrieb Erik Hesselink:
We've also used this approach to debug space-leaks, and would have
loved such a tool. We used deepseq, and compared the heap profiles. We
Hi,
Am Mittwoch, den 09.01.2013, 15:11 +0100 schrieb Erik Hesselink:
We finally solved the problems by completely moving
to strict map operations, strict MVar/TVar operations, and strict data
types.
do you mean strict by policy (i.e. before storing something in a
[MT]Var, you ensure it is
http://article.gmane.org/gmane.comp.lang.haskell.parallel/340
(with follow-up message about rseq = rdeepseq)
- J.W.
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Joachim Breitner m...@joachim-breitner.de wrote:
I’m wondering if the use of deepseq to avoid unwanted lazyness might
be a too large hammer in some use cases. Therefore, I’m looking for
real world programs with ample use of deepseq, and ideally easy ways
to test performance (so preferably no
surprisingly, deepseq is not used as much as I thought.
http://packdeps.haskellers.com/reverse/deepseq lists a lot of packages,
but (after grepping through some of the code) most just define NFData
instances and/or use it in tests, but rarely in the „real“ code. For
some reason I expected it
Hi,
Am Dienstag, den 08.01.2013, 13:01 -0800 schrieb Evan Laforge:
surprisingly, deepseq is not used as much as I thought.
http://packdeps.haskellers.com/reverse/deepseq lists a lot of packages,
but (after grepping through some of the code) most just define NFData
instances and/or use it
Dear Haskellers,
I’m wondering if the use of deepseq to avoid unwanted lazyness might be
a too large hammer in some use cases. Therefore, I’m looking for real
world programs with ample use of deepseq, and ideally easy ways to test
performance (so preferably no GUI applications).
I’ll try to find
There are two senses in which deepseq can be overkill:
1. The structure was already strict, and deepseq just forces another
no-op traversal of the entire structure. This hypothetically affects
seq too, although seq is quite cheap so it's not a problem.
2. deepseq evaluates too much, when it was
Hi,
Am Montag, den 07.01.2013, 13:06 +0100 schrieb Joachim Breitner:
I’m wondering if the use of deepseq to avoid unwanted lazyness might be
a too large hammer in some use cases. Therefore, I’m looking for real
world programs with ample use of deepseq, and ideally easy ways to test
performance
On Mon, Jan 7, 2013 at 4:06 AM, Joachim Breitner
m...@joachim-breitner.de wrote:
I’m wondering if the use of deepseq to avoid unwanted lazyness might be
a too large hammer in some use cases. Therefore, I’m looking for real
world programs with ample use of deepseq, and ideally easy ways to test
13 matches
Mail list logo
