3 ms·
These are all on enterprise grade SSDs. At 10GB of storage, you likely have more raw IO capacity than you'd get on an EC2 instance with EBS. Right now, it's bui
by mrkurt 12y ago
These are all on enterprise grade SSDs. At 10GB of storage, you likely have more raw IO capacity than you'd get on an EC2 instance with EBS. Right now, it's built for high performance Postgres users, not databases with a whole bunch of cold data and a minimal hot data set.
- marbemac 12y agoAh I did not realize that it's not on EBS (aws announced SSD EBS last June so I thought perhaps you guys jumped on that opportunity). What's the max # of connections? Does it scale with storage as well?
- mrkurt 12y agoWe're tuning the connection limits during beta, but it's not something we typically scale. We set that as high as we can without hurting stability, and then let people shoot themselves in the foot if they want. :) If you use it and run into connection limit issues, let us know and we'll gladly up them for you.
- nstott 12y agoWe don't apply any artificial limit on the number of connections, or the number of ops/s. We scale on storage / memory, we try to keep the storage and memory scaling to a defined ratio for optimal performance
- sk5t 12y agoYou might find the HikariCP guidance on connection pools with SSD interesting. Less disk waiting can mean a much smaller pool is optimal, to avoid unnecessary context switching, among other things. https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-...