So, I have been encountering performance issues on my monero node that runs on HDD

it seems the number of in peers will directly cause latency on doing RPC calls

Basically, the number of in peers, assuming they are all wallets downloading the blockchain, will be the number of locations in the database that the HDD must seek to

this can quickly waste seconds in seeking time trying to do a round serving all the in peers

Sounds about right. Just one comment: It's probably not wallets downloading the blockchain from your node, but other nodes - the "peers" that you see the number of

Hard disks, aka "rotating rust", are notorious for being slow with Monero daemons, especially for initial syncing, which can take a loooong time with a HDD

Everybody advices to everybody else to get a SSD as soon as possible :)

Speaking of, has anybody tried caching with solid state media while the actual database is kept on a larger spinning disk? How does that perform in such a case?

It should work reasonably well, because most transactions reference only recent blocks (1-2 years old at most)

So cache big enough to hold 2 years worth of transactions, will work fine

"So cache big enough to hold 2 years worth of transactions, will work fine" <- this is a info should be in #monero-docs IMO

sech1: thanks

But not sure if it will be enough for initial sync. Need someone to test it. It should be enough for running a synced node.

<s​yntheticbird:monero.social> iirc there was an xmr miner with an onion service that have made a detailed guide on how to use an ssd and hdd in a cache strategy with LVM for that

<s​yntheticbird:monero.social> he said it worked pretty good but I don't have the link anymore

Yeah I meant for the synched node since HDD would be bottleneck when first syncing

"Speaking of, has anybody tried caching with solid state media while the actual database is kept on a larger spinning disk? How does that perform in such a case?" << yes. Ravfx

I did Caching / Tiered storage test a few month ago. Before the March stress test. It did allow to sync on an hard drive in less than a day, like 15 hours. Using only LVM2 on linux, Make a LV for the monero storage on an HDD and add a cache on the LV, to be placed on the nvme drive. Note that caching have to be configured as "write-cache" and that is important as you want the last 64GB (or whatever) of the blockchain and so you don't want "read" to

Awesome. Thanks ofrnxmr and RavFX

Ravfx had a nice step-by-step guide up at one point

Per his explanation, lvm based setup should be straightforward.