2009/8/11 Jean-Philippe Bernardy :
>
> On Tue, Aug 11, 2009 at 6:44 PM, Colin McQuillan
> wrote:
>>
>> I found a leak that can't be fixed by seq. The *messages* buffer will
>> still save undo information including everything that was ever shown.
>> This patch will print increasingly big lines:
>
On Tue, Aug 11, 2009 at 6:44 PM, Colin McQuillan wrote:
>
> I found a leak that can't be fixed by seq. The *messages* buffer will
> still save undo information including everything that was ever shown.
> This patch will print increasingly big lines:
There are two issues here.
1. As I mentioned p
2009/8/11 Jean-Philippe Bernardy :
>
> On Mon, Aug 10, 2009 at 11:51 PM, Jean-Philippe
> Bernardy wrote:
>> On Mon, Aug 10, 2009 at 11:28 PM, Colin McQuillan
>> wrote:
>>
>>> Great news. Could you give a quick summary of how you did it?
>>
>> Step by step:
>> [...]
>
> GC time still increase afte
On Tue, Aug 11, 2009 at 2:39 PM, Gwern Branwen wrote:
> Maybe it's an artifact of measurement? You could be seeing
> http://hackage.haskell.org/trac/ghc/ticket/698
The editor really seems to get slower. (The measurement tool is 'top' btw).
Also, I'm not so concerned about the RTS loosing track o
On Tue, Aug 11, 2009 at 7:33 AM, Jean-Philippe
Bernardy wrote:
On Mon, Aug 10, 2009 at 11:51 PM, Jean-Philippe
Bernardy wrote:
On Mon, Aug 10, 2009 at 11:28 PM, Colin McQuillan wrote:
Great news. Could you give a quick summary of how you did it?
Step by step:
[...]
GC time still increase
On Mon, Aug 10, 2009 at 11:51 PM, Jean-Philippe
Bernardy wrote:
> On Mon, Aug 10, 2009 at 11:28 PM, Colin McQuillan
> wrote:
>
>> Great news. Could you give a quick summary of how you did it?
>
> Step by step:
> [...]
GC time still increase after, say, an hour of normal usage.
So I'd say there i
On Tue, Aug 11, 2009 at 10:04 AM, Colin McQuillan wrote:
> My apologies. I've pushed a fix for a leak in Pango as well (also mine
> :-( ) but the message didn't make it to this list.
Excellent. (You have to add your "communities" account to the google group
so that commit messages make it here).
2009/8/10 Jean-Philippe Bernardy :
>> Do you
>> know if it was a leak I introduced (in Vty) that was causing most of
>> the slowness, or were all the leaks important?
>
> Yep, the leaks around window region calculation were responsible for creating
> a lot of objects.
My apologies. I've pushed a
On Mon, Aug 10, 2009 at 11:28 PM, Colin McQuillan wrote:
> Great news. Could you give a quick summary of how you did it?
Yes, I was thinking to write a blog post about this. Maybe we can
discuss it here,
we'll see if a hash up is worthy of dissemination.
Step by step:
# Compile for profiling
$
On Mon, Aug 10, 2009 at 4:28 PM, Colin McQuillan wrote:
> Perhaps you could give some tips for Yi developers who want to be sure
> they aren't creating bugs in the future. Is just "-hc" cost-center
> stack profiling enough?
Indeed, this would be great. Presently, I'm just timing with the Pango
H
2009/8/10 Jean-Philippe Bernardy :
>
> Hi,
>
> With the recent fixes of memory leaks, much progress has been made in
> terms of speed.
> I'm not talking about super fast/low CPU usage mind you, but I think
> we're back to the
> speed of last year, if not faster. So if you had given up on Yi for a
Hi,
With the recent fixes of memory leaks, much progress has been made in
terms of speed.
I'm not talking about super fast/low CPU usage mind you, but I think
we're back to the
speed of last year, if not faster. So if you had given up on Yi for a
while because of speed, it might
be time to try ag
12 matches
Mail list logo
