Subject Re: [firebird-support] Re: replicating On Premise FB environment to AWS
Author Steve Wiser
1) How many of the processors are you actually using -- what is your load average?
2) How much of the memory are you using?
3) How much of the disk space are you using?  How large is the database?
4) Are these multiple databases that can be split up into separate servers?

Normally AWS seems to want you to use multiple smaller EC2 instances versus a single large one.  Separating them across AZs and using auto-scale groups is also along their lines of best practices.

One tip - use Amazon Linux on the instances as it has some kernel tweaks for performance enhancements on AWS versus the stock CentOS image.


On Wed, May 23, 2018 at 10:42 AM, edmendeznc@... [firebird-support] <> wrote:

Currently we have several FIREBIRD Databases on premise. We are now looking to replicate one of our on premise Firebird environments to AWS.


On Premise we are running Firebird 2.5.4 Classic on Linux CENTOS

CPU – 64 cores

Memory – 256GB

Disk – 9TB Raid 10 array.

We typically have around 120 connections at peak times.

This DB is mainly for reporting, so there are a good portion of reports are long running queries, and many are not so long running queries.


Now on AWS you now have many options for the EC2 instances.


I am looking for guidance as to which EC2 instance would be a good fit, and anyone has come across documentation on running Firebird on AWS. I came across the Firebird_Hardware_Guide_ IBSurgeon.pdf but that doesn’t speak to using it on AWS EC2.


Thank you in advance.


-Edward Mendez