[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Improving client side performance of pulls
From: |
Matt Johnston |
Subject: |
Re: [Monotone-devel] Improving client side performance of pulls |
Date: |
Wed, 2 Aug 2006 16:19:53 +0800 |
User-agent: |
Mutt/1.5.11+cvs20060403 |
On Wed, Aug 02, 2006 at 01:14:43AM -0700, Eric Anderson wrote:
> I've been looking into the cpu usage of pulls on the client. Below is
> the oprofile sampling from doing a pull of the monotone database,
> measuring only the client. Note that to actually get useful data on
> where time is spent not in the monotone code itself, I found I had to
> statically link to get the symbols for decoding.
>
> 412229 7.8868 __pthread_alt_unlock
> 364334 6.9705 __pthread_alt_lock
> 333146 6.3738 memset
> Does anyone have some other ideas? All of these solutions seem bad.
> If there aren't other ideas, opinions on which is the "least-bad"?
Just wondering, does -fno-threadsafe-statics make any
difference? It does on OS X, though I think that may be a
platform-specific bug.
Matt