Size/Config of DB Repository

[Ed Lucas]

Hi,

We're a small shop, one location, that just purchased Corporate with a block of floaters for our key staff.  We're thinking that we want to install EA on top of MySQL and version control the models at the package level using our existing svn.

My question is this:  Do you have any recommendations on the sizing or configuration of the database server?  Can we just slap MySQL on a 10-year-old Dell P3 pizza box with 512 MB RAM and a 40 GB disk and be good to go?  Do we need something bigger/faster?  How about virtualization?  Should we crank up a VM to put the DB into?  If so, how should we allocate resources?

To give you a bit more context, I have a couple local .EAP files that are 20-30 MB, and that's just scratching the surface in those problem domains.  I imagine eventually having 5x-10x the information within each model and having dozens of models.

Does any of this even matter?  I appreciate your input.  Thanks!

-- Ed

[Geert Bellekens]

Ed,

When using EA with a db config you don't really need to worry about the db server's cpu time (or memory I think).
The main bottleneck is the chattiness of the EA client.
Every second hundreds of small queries are being sent to the database server, which all have to be packaged and sent over the network. So if anything, look at a decent network connection.

I don't really think you will notice a big difference when you upgrade the hardware specs of your server box.

Geert