đź“… Original date posted:2012-07-27
đź“ť Original message:On Fri, Jul 27, 2012 at 1:59 AM, grarpamp <grarpamp at gmail.com> wrote:
>> I now have an 1.8 ghz p3 celeron (128k cache) which should be
>> substantially slower than your machine, running vintage 2.6.20 linux.
>> Unfortunately I forgot to turn on timestamp logging so I don't know
>> how long it took to sync the chain, but it was less than two days as
>> that was the span between when I checked on it. It's staying current
>
> Well, are you running bitcoin on, say, an FS with sha256 integrity
> trees for all bits and AES-128-XTS/CBC disk encryption?
> If not, we're not comparing the same apples, let alone the same OS.
The file system is using twofish-cbc-essiv:sha256, apparently. (I
went and dug up a mothballed machine of mine because of your post).
And I agree, encrypting everything is a good practice— I once got a
disk back from RMA where only the first sectors were zeroed and the
rest had someone elses data, since then I've encrypted everything
because you can't wipe a dead drive.
I'd love to know precisely what Bitcoin is doing thats making your
machine so unhappy... but your configuration is uncommon for bitcoin
nodes in many distinct ways so it's not clear where to start.
Gregory Maxwell [ARCHIVE] /
npub1f2…crwet
2023-06-07 10:25:30
in reply to nevent1q…lmwt
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwetPublished at
2023-06-07 10:25:30Event JSON
{
"id": "69a86679a6cf644627c6d39c7dfb6460ec9130a29a02689c6119c7527c625a42",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686133530,
"kind": 1,
"tags": [
[
"e",
"63aed588f060c9675f9ddd34399756623e96cc693cda2679b108affeaacc7675",
"",
"root"
],
[
"e",
"0a2d1905108fc27e8a2b77a2d48569328d43eb34d7bb6dc98c1871c68d9f31ce",
"",
"reply"
],
[
"p",
"1c840f1e75d7845e20cc48358219b63ce235ccf72a89298d799e6bda2907af87"
]
],
"content": "📅 Original date posted:2012-07-27\n📝 Original message:On Fri, Jul 27, 2012 at 1:59 AM, grarpamp \u003cgrarpamp at gmail.com\u003e wrote:\n\u003e\u003e I now have an 1.8 ghz p3 celeron (128k cache) which should be\n\u003e\u003e substantially slower than your machine, running vintage 2.6.20 linux.\n\u003e\u003e Unfortunately I forgot to turn on timestamp logging so I don't know\n\u003e\u003e how long it took to sync the chain, but it was less than two days as\n\u003e\u003e that was the span between when I checked on it. It's staying current\n\u003e\n\u003e Well, are you running bitcoin on, say, an FS with sha256 integrity\n\u003e trees for all bits and AES-128-XTS/CBC disk encryption?\n\u003e If not, we're not comparing the same apples, let alone the same OS.\n\nThe file system is using twofish-cbc-essiv:sha256, apparently. (I\nwent and dug up a mothballed machine of mine because of your post).\n\nAnd I agree, encrypting everything is a good practice— I once got a\ndisk back from RMA where only the first sectors were zeroed and the\nrest had someone elses data, since then I've encrypted everything\nbecause you can't wipe a dead drive.\n\nI'd love to know precisely what Bitcoin is doing thats making your\nmachine so unhappy... but your configuration is uncommon for bitcoin\nnodes in many distinct ways so it's not clear where to start.",
"sig": "3bbd4186f01bc3fbb0b0282b6719281a3271266d2d5222717cc5c2d4b65b247b8d3a4ce456a28fe9097f093884695b7d86c083d105d459e85117294a7e23444c"
}