📅 Original date posted:2015-10-13
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
You wanted advice... you got it
Jonathan Toomim (Toomim Bros):
>
> On Oct 13, 2015, at 3:49 PM, odinn
> <odinn.cyberguerrilla at riseup.net> 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 Linux server 3.2.0-4-amd64 #1 SMP
> Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux Linux prime 3.2.0-4-amd64
> #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux
>
> This excessive memory consumption was seen on 3 machines, all of
> which run Debian. All three machines run p2pool as well as
> bitcoind. Two run XT, one runs Core.
>
>>
>> You should compare this to having set up a node on a completely
>> clean computer.
>
>
> I can't afford to do that. All of the servers I have are being used
> for something. Also, I'm not sure what it is you're trying to test
> for with that suggestion. The numbers I'm reporting are for
> bitcoind's resident set, not for the whole server's memory usage. I
> don't see how other processes running on the same machine are
> relevant unless you are suggesting that RPC calls (e.g.
> getblocktemplate) might be somehow responsible.
>
>>
>> Also, dump your XT, is poo.
>
>
> Not relevant. I addressed this message to both the Core and XT
> lists because the issue appears to affect both forks. Let's keep
> blocksize and governance debates to their own threads, please.
>
> Repeating request: Has anyone else seen something similar? Can you
> report your mempool size and total bitcoind resident set size for
> your running full nodes?
>
- --
http://abis.io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
https://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCgAGBQJWHZrZAAoJEGxwq/inSG8CZzQIAKsqKs//Wydv60nXgy5AWAPU
qZ9HuyyWXDKljxzv/Ky5jS7o7B8Ivhnt6zWvkpMTF/R9MLpGrS9jBxXZjHF//ET0
L+eoVrmxwt+rgSjIPSGU/ftF8Jnh1sELecR8FMuCaFR87xraR/7FsJF/233RLWFg
+scNiFEgttyizFNgSq2r1/N3G5e603qXfh0+reaabDX3E+8+PKyUqVaG5E+TUEW0
NIkqi7MuEYd+/Q0SGAYyY/j2BQnebsTB2TbupE/soJkAYqYbCQR8TtrctmwLXTL0
GN+WyWwLYpMio3+7a6oQJ67TBcFxCVmF81zxKM1VIoT0u39VVWeYD1YfxEYFN9Y=
=a6kH
-----END PGP SIGNATURE-----
odinn [ARCHIVE] /
npub1xv…5j2ga
2023-06-07 17:43:17
in reply to nevent1q…swds
Author Public Key
npub1xv3g4rkhj7eyape0cqjhc9g4ljdu5axqkgcdewma854a8r7e0mtsl5j2gaPublished at
2023-06-07 17:43:17Event JSON
{
"id": "abe449d7d80c0a1f5b2e6de2f2cb7fc01a15487bdf6a9255332eff4e4c65a96f",
"pubkey": "33228a8ed797b24e872fc0257c1515fc9bca74c0b230dcbb7d3d2bd38fd97ed7",
"created_at": 1686159797,
"kind": 1,
"tags": [
[
"e",
"257c60cbd2c94bcbc1af242f96780d9665ec0aa19ec5454bed0371ff096c7c39",
"",
"root"
],
[
"e",
"7a1617afd579915c67e02c04d3343b81b52c0fcd72d1cdb3f754d5b484fb16ba",
"",
"reply"
],
[
"p",
"a384795310cea1937dda4d01ee8f14ca734b9a7ab60c62114a5656706e15e47f"
]
],
"content": "📅 Original date posted:2015-10-13\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\nYou wanted advice... you got it\n\nJonathan Toomim (Toomim Bros):\n\u003e \n\u003e On Oct 13, 2015, at 3:49 PM, odinn\n\u003e \u003codinn.cyberguerrilla at riseup.net\u003e wrote:\n\u003e \n\u003e\u003e Signed PGP part It would also help to know what operating\n\u003e\u003e system(s) you are using for both the oldie and the freshie.\n\u003e \n\u003e Linux feather 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3\n\u003e (2015-08-04) x86_64 GNU/Linux Linux server 3.2.0-4-amd64 #1 SMP\n\u003e Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux Linux prime 3.2.0-4-amd64\n\u003e #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux\n\u003e \n\u003e This excessive memory consumption was seen on 3 machines, all of\n\u003e which run Debian. All three machines run p2pool as well as\n\u003e bitcoind. Two run XT, one runs Core.\n\u003e \n\u003e\u003e \n\u003e\u003e You should compare this to having set up a node on a completely\n\u003e\u003e clean computer.\n\u003e \n\u003e \n\u003e I can't afford to do that. All of the servers I have are being used\n\u003e for something. Also, I'm not sure what it is you're trying to test\n\u003e for with that suggestion. The numbers I'm reporting are for\n\u003e bitcoind's resident set, not for the whole server's memory usage. I\n\u003e don't see how other processes running on the same machine are\n\u003e relevant unless you are suggesting that RPC calls (e.g.\n\u003e getblocktemplate) might be somehow responsible.\n\u003e \n\u003e\u003e \n\u003e\u003e Also, dump your XT, is poo.\n\u003e \n\u003e \n\u003e Not relevant. I addressed this message to both the Core and XT\n\u003e lists because the issue appears to affect both forks. Let's keep\n\u003e blocksize and governance debates to their own threads, please.\n\u003e \n\u003e Repeating request: Has anyone else seen something similar? Can you\n\u003e report your mempool size and total bitcoind resident set size for\n\u003e your running full nodes?\n\u003e \n\n- -- \nhttp://abis.io ~\n\"a protocol concept to enable decentralization\nand expansion of a giving economy, and a new social good\"\nhttps://keybase.io/odinn\n-----BEGIN PGP SIGNATURE-----\n\niQEcBAEBCgAGBQJWHZrZAAoJEGxwq/inSG8CZzQIAKsqKs//Wydv60nXgy5AWAPU\nqZ9HuyyWXDKljxzv/Ky5jS7o7B8Ivhnt6zWvkpMTF/R9MLpGrS9jBxXZjHF//ET0\nL+eoVrmxwt+rgSjIPSGU/ftF8Jnh1sELecR8FMuCaFR87xraR/7FsJF/233RLWFg\n+scNiFEgttyizFNgSq2r1/N3G5e603qXfh0+reaabDX3E+8+PKyUqVaG5E+TUEW0\nNIkqi7MuEYd+/Q0SGAYyY/j2BQnebsTB2TbupE/soJkAYqYbCQR8TtrctmwLXTL0\nGN+WyWwLYpMio3+7a6oQJ67TBcFxCVmF81zxKM1VIoT0u39VVWeYD1YfxEYFN9Y=\n=a6kH\n-----END PGP SIGNATURE-----",
"sig": "ad30f1d6e0f7a27e362385d4fc429d2eea6250b01d658ec940b384b2f31fcb939eb83cd1409242cee2dce4b6eb27dc769661511d0ba85171ec2ca61ea6251755"
}