user6918: I currently have cardano-node and db-sync running on the same machine. The machine has a max RAM capacity of 32 GB and this is barely enough. Instead of buying a new machine that supports 64 GB RAM, I could use another machine I have of 32 GB RAM, to run only db-sync, on the same LAN as cardano-node.
I'd like to hear from anyone that has run cardano-node and db-sync both on the same machine as well as on different machines on the same LAN to see if you decided it had to be both cardano-node and db-sync on the same machine because on separate machines proved too slow?

user4413: I'm running cardano-db-sync on the same machine of cardano-node. The machine is also a block-producer (--nonmoving-gc), cardano-wallet provider, cncli sendtip provider. The amount of RAM needed ended up to be 64GB.
The main reason driving me to host everything on the same machine is that it's a virtual machine that I can fine-tune whenever I want.
Also, you should consider this: cardano-db-sync needs a --socket-path path specified. That means that you can't straightforwardly run cardano-node and cardano-db-sync on different machines. You can probably play around with netcat to redirect I/O to/from the socket to/from a TCP socket, or mount remotely the path where the socket is located.

user252: A very big chunk of memory usage for dbsync comes from ledger-state - you can disable this component if you do not require things like epoch_stake, ada_pots, etc.
You can read more about it here.
If you do require these, 48GB RAM IMO is bar minimum, and 64GB is ideal (for instance, if you optimise Postgres configurations to serve more processing capacity and less IO dependency)

user5122: Yes, you can do it. Run cardano-node on one of the machines and cardano-db-sync on the other, and use socat to connect from the cardano-db-sync machine to the cardano-node's socket file. This is how I am doing it.

6918: <p>I currently have cardano-node and db-sync running on the same machine. The machine has a max RAM capacity of 32 GB and this is barely enough. Instead of buying a new machine that supports 64 GB RAM, I could use another machine I have of 32 GB RAM, to run only db-sync, on the same LAN as cardano-node.</p>
<p>I'd like to hear from anyone that has run cardano-node and db-sync both on the same machine as well as on different machines on the same LAN to see if you decided it had to be both cardano-node and db-sync on the same machine because on separate machines proved too slow?</p>
 4413: <p>I'm running <code>cardano-db-sync</code> on the same machine of <code>cardano-node</code>. The machine is also a <code>block-producer</code> <code>(--nonmoving-gc)</code>, <code>cardano-wallet</code> provider, <code>cncli sendtip</code> provider. The amount of RAM needed ended up to be <strong>64GB</strong>.</p>
<p>The main reason driving me to host everything on the same machine is that it's a virtual machine that I can fine-tune whenever I want.</p>
<p>Also, you should consider this: <code>cardano-db-sync</code> needs a <code>--socket-path path</code> specified. That means that you can't straightforwardly run <code>cardano-node</code> and <code>cardano-db-sync</code> on different machines. You can probably play around with netcat to redirect I/O to/from the socket to/from a TCP socket, or mount remotely the path where the socket is located.</p>
 252: <p>A very big chunk of memory usage for dbsync comes from <code>ledger-state</code> - you can disable this component if you do not require things like <code>epoch_stake</code>, <code>ada_pots</code>, etc.
You can read more about it <a href="https://github.com/input-output-hk/cardano-db-sync/blob/master/doc/configuration.md#--disable-ledger" rel="nofollow noreferrer">here</a>.</p>
<p>If you do require these, 48GB RAM IMO is bar minimum, and 64GB is ideal (for instance, if you optimise Postgres configurations to serve more processing capacity and less IO dependency)</p>
 5122: <p>Yes, you can do it. Run cardano-node on one of the machines and cardano-db-sync on the other, and use socat to connect from the cardano-db-sync machine to the cardano-node's socket file. This is how I am doing it.</p>
