Group conduit and algod along with storage.

README.md

@@ -34,8 +34,9 @@ All recommendations here should be be used as a starting point. Further benchmar
 For a simple deployment the following configuration works well:
 * Network: Indexer, Conduit, Algod and PostgreSQL should all be on the same network.
 * Indexer: 1 CPU and 1GB of ram. Scale up for systems with high query volume.
-* Conduit/Algod: 4 CPU and 8 GB of ram.
+* Conduit + Algod: 4 CPU and 8 GB of ram.
   * Storage: algod follower nodes, 40 GiB, 3000 IOPS minimum.
+  * Deployments allocating less ram might work in conjunction with [GOMEMLIMIT](https://pkg.go.dev/runtime@master#hdr-Environment_Variables) for Algod (and even Conduit). This configuration is not tested, so use with caution and monitor closely.
 * Database: When hosted on AWS a `db.r5.xlarge` instance works well.
 
 A database with replication can be used to scale read volume. Configure a single Conduit writer with multiple Indexer readers.