📅 Original date posted:2015-10-13
📝 Original message: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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151013/f11fac76/attachment-0001.html>;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151013/f11fac76/attachment-0001.sig>;
Jonathan Toomim (Toomim Bros) [ARCHIVE] /
npub156…9r5gn
2023-06-07 17:43:16
in reply to nevent1q…vme4
Author Public Key
npub156vplpc5zjxk79ttdc320xhwq385tchgryp90hyzna9pju8yhn8s69r5gnPublished at
2023-06-07 17:43:16Event JSON
{
"id": "ceca0dfd02f00417b95d6cba823e71c61a9b51d579424ddb1d824be8bef4c188",
"pubkey": "a6981f8714148d6f156b6e22a79aee044f45e2e8190257dc829f4a1970e4bccf",
"created_at": 1686159796,
"kind": 1,
"tags": [
[
"e",
"257c60cbd2c94bcbc1af242f96780d9665ec0aa19ec5454bed0371ff096c7c39",
"",
"root"
],
[
"e",
"82cb6317898ed2b25c6975f7e13480905e113d0afb9ad07df15c72cc5adef118",
"",
"reply"
],
[
"p",
"33228a8ed797b24e872fc0257c1515fc9bca74c0b230dcbb7d3d2bd38fd97ed7"
]
],
"content": "📅 Original date posted:2015-10-13\n📝 Original message:On Oct 13, 2015, at 3:49 PM, odinn \u003codinn.cyberguerrilla at riseup.net\u003e wrote:\n\n\u003e Signed PGP part\n\u003e It would also help to know what operating system(s) you are\n\u003e using for both the oldie and the freshie.\n\nLinux feather 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux\nLinux server 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux\nLinux prime 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux\n\nThis 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.\n\n\u003e \n\u003e You should compare this to having set up a node on a completely clean\n\u003e computer.\n\n\nI 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.\n\n\u003e \n\u003e Also, dump your XT, is poo.\n\n\nNot 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.\n\nRepeating request: Has anyone else seen something similar? Can you report your mempool size and total bitcoind resident set size for your running full nodes?\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151013/f11fac76/attachment-0001.html\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 496 bytes\nDesc: Message signed with OpenPGP using GPGMail\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151013/f11fac76/attachment-0001.sig\u003e",
"sig": "caa0b05148c351399edb3a6c1f7ef9c3c33cfc5de096026f48a1795c05b9fb0e2bd54112ff054da1a35fc99a072f74bad84b91c0ac00968bf8ec89f616e99eb6"
}