bitcoin core – Outdated non-HD pockets.dat caught round 96.21% after IBD seems full — pockets rescan or bottleneck?

I’m making an attempt to know the state of an previous Bitcoin Core pockets synchronization / rescan.

Context:

• Pockets sort: previous legacy / non-HD pockets.dat, seemingly created round 2009–2011
• Machine: devoted MacBook Professional 2022/2023
• Bitcoin Core runs 24/7
• Sleep is disabled by way of: sudo pmset -a disablesleep 1
• The machine is used just for Bitcoin Core
• Web connection is steady LAN / fiber
• Present GUI progress: about 96.21%
• First documented progress: 94.46% on 2023-11-19
• Necessary later factors:
  • 2025-12-21: 96.00%
  • 2026-01-15: 96.04%
  • 2026-02-27: 96.10%
  • 2026-04-17: 96.17%
  • present: 96.21%
• The information listing is round 80 GB
• The GUI presently exhibits 0.00000000 BTC
• I used to be advised there could also be many keys within the pockets keypool, probably tons of or 1000’s
• I used to be additionally advised that round 36,612 blocks should still be open / unprocessed

In debug.log I repeatedly see strains like:

UpdateTip … progress=1.000000

I additionally see a number of strains like:

[net:warning] pcp: Couldn’t obtain response: Connection refused (61)

I do NOT see apparent errors corresponding to:

• corrupt
• database error
• pockets.dat corrupt
• can not rescan past pruned top
• reindex required

My questions:

Outdated legacy/non-HD pockets.dat: Bitcoin Core has been extraordinarily sluggish since 2023. The GUI is presently at 96.21%, the pockets exhibits 0 BTC, and debug.log repeatedly exhibits UpdateTip ... progress=1.000000 with no seen DB/corruption errors.

Does this point out a standard however very sluggish pockets rescan/DB bottleneck after accomplished IBD, or does it counsel a configuration/downside state?

thanks upfront!

I’m making an attempt to know the state of an previous Bitcoin Core pockets synchronization / rescan.

Context:

• Pockets sort: previous legacy / non-HD pockets.dat, seemingly created round 2009–2011
• Machine: devoted MacBook Professional 2022/2023
• Bitcoin Core runs 24/7
• Sleep is disabled by way of: sudo pmset -a disablesleep 1
• The machine is used just for Bitcoin Core
• Web connection is steady LAN / fiber
• Present GUI progress: about 96.21%
• First documented progress: 94.46% on 2023-11-19
• Necessary later factors:
  • 2025-12-21: 96.00%
  • 2026-01-15: 96.04%
  • 2026-02-27: 96.10%
  • 2026-04-17: 96.17%
  • present: 96.21%
• The information listing is round 80 GB
• The GUI presently exhibits 0.00000000 BTC
• I used to be advised there could also be many keys within the pockets keypool, probably tons of or 1000’s
• I used to be additionally advised that round 36,612 blocks should still be open / unprocessed

In debug.log I repeatedly see strains like:

UpdateTip … progress=1.000000

I additionally see a number of strains like:

[net:warning] pcp: Couldn’t obtain response: Connection refused (61)

I do NOT see apparent errors corresponding to:

• corrupt
• database error
• pockets.dat corrupt
• can not rescan past pruned top
• reindex required

My questions:

Outdated legacy/non-HD pockets.dat: Bitcoin Core has been extraordinarily sluggish since 2023. The GUI is presently at 96.21%, the pockets exhibits 0 BTC, and debug.log repeatedly exhibits UpdateTip ... progress=1.000000 with no seen DB/corruption errors.

Does this point out a standard however very sluggish pockets rescan/DB bottleneck after accomplished IBD, or does it counsel a configuration/downside state?

thanks upfront!