The "on hold" notice placed on your question included a link to the Help Centre, which I repeated in a comment on your question here. To quote:
Questions that need additional work or that are not a good fit for this site may be put on hold by experienced community members. While questions are on hold, they cannot be answered, but can be edited to make them eligible for reopening.
It would have been better to edit your question to improve it as suggested, rather than simply deleting it.
Regarding the "shopping list" reason, we generally discourage questions of that sort because they:
- Can be very open-ended, leading to extended discussion
- Go out of date very quickly
- Tend to attract link-only and spam answers
See: Q&A is Hard, Let's Go Shopping!
Thus, when it comes to shopping questions, don't ask us what you should buy - ask us what you need to learn to tell what you should buy.
The relevant point is that asking for the specific hardware you need is much less useful on Q & A sites than a question that asks how you should go about determining what sort of hardware you need for a particular workload; for instance, what sort of things you should measure.
That said, a very well-asked question about the hardware needed for your specific circumstances might still be answered and not closed as off-topic by our community - but it would have to be very clear and precise, with much more relevant information than the first version of your question.
The latest version of your question (at the time of writing) is making progress in the right direction, by mentioning the hardware you are currently using (and revealing it as a cloud-based deployment for the first time).
The question currently has 3 reopen votes (of the 5 needed). Further edits in light of the information above and submitted in comments and answers to this meta question can only help bring this question to a state where it is properly on-topic and answerable.
Update: the community have now voted to reopen this question.
many connections
. Actually you can reach to correct hardware specs after round of testing and specifically testing I/O responses. You also need to knownumber of connections
andconcurrent users
. I have worked VERY LTTLE with Postgresql but the method holds same for all RDBMS