Now, eagle-eyed readers looking at the screenshots of the terminal may see that the previous run took 24.5 minutes, while this one took only 13 minutes.
Alas, that difference in execution time *was not* a real increase in execution speed.
I suspect that either the cable that is connected to the back of the RAID wasn’t properly seated when I created the first screenshot, and/or the system had been in a weird state, which was cleared by its weekly Sunday morning reboot.
Denis Warburton /
npub1gw…hfu48
2024-10-14 00:50:30
in reply to nevent1q…xw9m
Author Public Key
npub1gw6zu5t0csg4z6aj58urm7h9q529ehnav3zp3nplq8j6fhcj6lzsuhfu48Published at
2024-10-14 00:50:30Event JSON
{
"id": "559d6ea57993c99b8b886d4c69be9378ec3e9df671190e5f2d551200ac2ee3bc",
"pubkey": "43b42e516fc411516bb2a1f83dfae505145cde7d644418cc3f01e5a4df12d7c5",
"created_at": 1728867030,
"kind": 1,
"tags": [
[
"e",
"0f6c85fbbf528baa20d15f73ee790482915e04ea53e6005e355c5fc8a2d11e26",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://digipres.club/users/artandtechnic/statuses/113303029741627295",
"activitypub"
]
],
"content": "Now, eagle-eyed readers looking at the screenshots of the terminal may see that the previous run took 24.5 minutes, while this one took only 13 minutes.\n\nAlas, that difference in execution time *was not* a real increase in execution speed.\n\nI suspect that either the cable that is connected to the back of the RAID wasn’t properly seated when I created the first screenshot, and/or the system had been in a weird state, which was cleared by its weekly Sunday morning reboot.",
"sig": "eed4545e6ea18ac21f443964521c6b7f8880971d02323dcc2ce893891a4b9e8901ab091ab468a4918a34b3c3af53702c44882c8690d34039edc6fa45dbfd25bd"
}