Btc Drak via bitcoin-dev writes:
> I think this thread has gotten to the stage where it should be moved
> to an issue on Github and not continue to CC the bitcoin-dev list (or
> any other list tbh).
Agreed. I couldn't see an issue, so I've opened one.
I think this thread has gotten to the stage where it should be moved
to an issue on Github and not continue to CC the bitcoin-dev list (or
any other list tbh).
On Thu, Oct 22, 2015 at 5:27 PM, Jonathan Toomim via bitcoin-dev
wrote:
> You may want to add a
The method I was using was essentially
grep VmRSS /proc/$pid/status
Comparing these two methods, I get
Your method (PSS):
2408313
My method (RSS):
VmRSS: 2410396 kB
On Oct 21, 2015, at 12:29 AM, Tom Zander wrote:
> On Tuesday 20 Oct 2015
On Tuesday 20 Oct 2015 20:01:16 Jonathan Toomim wrote:
> claimed that he had this memory usage issue on Linux, but not on Mac OS X,
> under a GBT workload in both situations. If this is true, that would
> suggest this might be a fragmentation issue due to poor memory allocation.
Please make sure
On Wed, Oct 21, 2015 at 2:01 PM, Jonathan Toomim wrote:
> 3. One user on the bitcointalk p2pool thread (
> https://bitcointalk.org/index.php?topic=18313.msg12733791#msg12733791)
> claimed that he had this memory usage issue on Linux, but not on Mac OS X,
> under a GBT workload in
I did that Sunday twice. I'll report the results soon. Short version is that it
looks like valgrind is just finding 200 kB to 600 kB of pblocktemplate, which
is declared as a static pointer. Not exactly the multi-GB leak I'm looking for,
but possibly related.
I've also got two bitcoind
More notes:
1. I ran a side-by-side comparison with two bitcoind processes (Core, same
recent git commit as before) on the same computer with the same settings
running on different ports. With both processes, I logged RSS (via
/proc/$pid/status) every 6 seconds. With one of those processes, I
My nodes are continuously running getblocktemplate and getinfo, and I also
suspected the issue is in either gbt or the rpc server.
The instance only takes a few hours to get up to that memory usage.
On Oct 18, 2015 8:59 AM, "Jonathan Toomim via bitcoin-dev" <
I should also mention that this is definitely not an attack coming from
connected nodes. My node experiencing the issue is only connected to 3
other nodes, all of which I control (via connect=).
--Adam
On Mon, Oct 19, 2015 at 12:17 PM, Multipool Admin
wrote:
> My nodes are
I can do better than that:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
10625 20 0 41.310g 0.035t 51172 S 1.0 57.6 47:11.17
bitcoind
Any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
For the record, Mr. Hearn, you do not own this list. I submit to you
that you have very little to say on this matter at this stage and your
idle threats to "ban people" based on their preferences, suggestions,
or characterizations of your chosen
Leaks are not the only explanation possible. Caches and fragmentation can
also give this sort of effect. Unfortunately the tools to debug this aren't
great. You could try a build with tcmalloc and use it to investigate heap
stats.
Odinn, trolling like a 3 year old will get you swiftly banned.
> I just noticed that several of my running bitcoind processes were using
> around 3+ GB of RAM, even though the mempool itself seemed to be under
> control.
>
> @prime:~/bin$ ./bitcoin-cli getmempoolinfo
> {
> "size" : 1896,
> "bytes" : 37341328
> }
>
> [total memory usage not
On Tue, Oct 13, 2015 at 02:56:08PM -0700, Jonathan Toomim (Toomim Bros) via
bitcoin-dev wrote:
> I just noticed that several of my running bitcoind processes were using
> around 3+ GB of RAM, even though the mempool itself seemed to be under
> control.
>
> @prime:~/bin$ ./bitcoin-cli
It was about 360MB (30 minutes ago?), but is now about 460MB. I'm sure it
won't keep going up that fast.
{
"size" : 3413,
"bytes" : 41892350
}
On Tue, Oct 13, 2015 at 5:08 PM, Jonathan Toomim (Toomim Bros)
wrote:
> 16 million divided by 1085 transactions is almost 15Kb per
On Oct 13, 2015, at 3:49 PM, odinn wrote:
> Signed PGP part
> It would also help to know what operating system(s) you are
> using for both the oldie and the freshie.
Linux feather 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04)
x86_64 GNU/Linux
{
"size" : 1085,
"bytes" : 16151768
}
It has been running about a day. I'll report tomorrow too. This is a
Windows 8.1 box.
16 million divided by 1085 transactions is almost 15Kb per transaction =
unlikely, right?
On Tue, Oct 13, 2015 at 4:14 PM, Jonathan Toomim (Toomim Bros)
> 16 million divided by 1085 transactions is almost 15Kb per transaction =
> unlikely, right?
The recent spam was about 15 kB per transaction, so that part sounds right.
The anomalous thing that I saw was that the total bitcoind process usage was
about 50-100x higher than I would have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
You should compare this to having set up a node on a completely clean
computer. It would also help to know what operating system(s) you are
using for both the oldie and the freshie.
Also, dump your XT, is poo. Then try again, look at Core nodes
19 matches
Mail list logo