summaryrefslogtreecommitdiff
path: root/0c/5c0ca6e3ee5382dee27131a0cc965bcaa2f1d1
blob: 34d8e047dd8147ed833c5731df9ff6ddd69529d3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gronager@ceptacle.com>) id 1S0esQ-0002yW-9H
	for bitcoin-development@lists.sourceforge.net;
	Thu, 23 Feb 2012 20:02:54 +0000
X-ACL-Warn: 
Received: from 2508ds5-oebr.0.fullrate.dk ([95.166.54.49]
	helo=mail.ceptacle.com)
	by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1S0esP-0000Zp-2t for bitcoin-development@lists.sourceforge.net;
	Thu, 23 Feb 2012 20:02:54 +0000
Received: from localhost (localhost [127.0.0.1])
	by mail.ceptacle.com (Postfix) with ESMTP id B39EC17CFD6F;
	Thu, 23 Feb 2012 21:02:46 +0100 (CET)
X-Virus-Scanned: amavisd-new at ceptacle.com
Received: from mail.ceptacle.com ([127.0.0.1])
	by localhost (server.ceptacle.private [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id YHFCi2LGmp9m; Thu, 23 Feb 2012 21:02:46 +0100 (CET)
Received: from [10.0.1.28] (2508ds5-oebr.0.fullrate.dk [95.166.54.49])
	by mail.ceptacle.com (Postfix) with ESMTPSA id 559BB17CFD5E;
	Thu, 23 Feb 2012 21:02:46 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Michael Gronager <gronager@ceptacle.com>
In-Reply-To: <81E27E9B-BD4B-4429-BF91-FED3505CE6D0@ceptacle.com>
Date: Thu, 23 Feb 2012 21:02:46 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3428A99D-3E68-4E06-9DD1-83741C9CDD42@ceptacle.com>
References: <81E27E9B-BD4B-4429-BF91-FED3505CE6D0@ceptacle.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
X-Mailer: Apple Mail (2.1257)
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1S0esP-0000Zp-2t
Subject: Re: [Bitcoin-development] BitcoinQt eating 100% CPU
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2012 20:02:54 -0000

A follow up on my mail from the other day (got it send from the wrong =
email address...)

I now exit the ipc thread at startup by inserting:

void ipcThread(void* parg)
{
   ipcShutdown();
   return;

Bitcoin-Qt is now running nicely using around 0.9% CPU. So it seems like =
the culprit was indeed line 31:

if(mq->timed_receive(&strBuf, sizeof(strBuf), nSize, nPriority, d))

Others, who have seen similar issues ?

Cheers,

M=20

On 21/02/2012, at 21:33, Michael Gr=F8nager wrote:

> Hi Wladimir / others,
>=20
> I just downloaded the latest (0.6 rc1) source of bitcoin-qt and built =
it using qt-creator on MacOSX 10.7.3. Nice and easy experience, even =
though I had to change BDB version to 5.1 ;)
>=20
> However, when running it, it is using 100% CPU (after initial block =
chain download that is...)
> * All activity in debug.log seems normal (blocks/txes/addresses are =
processes and accepted etc) so it is not stuck (at least not in the =
MessageThread)
> * Sampling the process shows that the majority of time in each thread =
is used for:
> ** __semwait_signal
> ** kevent
> ** __select
> ** mach_msg_trap
> ** boost::date_time::micro_sec_clock
>=20
> None of this would usually alert me - sleeping and waiting for =
conditions should not consume CPU, the only issue seems to be the last =
line which is called from qtipcserver.cpp line 31:
>=20
>      if(mq->timed_receive(&strBuf, sizeof(strBuf), nSize, nPriority, =
d))
>=20
> As I see it this should not consume cpu either, but, it is the only =
thing that seems a bit strange..
>=20
> Have you seen this before?
>=20
> /M