<< Make the 2.4 GHz server the database server, it will give you the best
growth-path (it is easier to serve many webservers from one database server as one
webserver from many database servers). >>
Thanks Jochem. I failed to say that we've got a one to one website to database
relationship. O
Jeff Horne wrote:
> << How large are the databases? >>
>
> Not very large. 474mb for all.
> << Are your databases CPU bound or I/O bound? >>
>
> I/O bound.
Why are you I/O bound when you should have enough RAM to cache all
databases completely?
Make the 2.4 GHz server the database server, it
<< How large are the databases? >>
Not very large. 474mb for all.
<< What are the specs of the disks? >>
I'm not sure what you mean.
<< Are your databases CPU bound or I/O bound? >>
I/O bound.
Thanks,
Jeff
~|
Archives: http
Horne, Jeff wrote:
> We have two servers to choose from for loading CF. One is a current CF
> webserver, the other is a new webserver that will be used for MySQL
> databases. My dilema is, since I have the option now, which one do I want
> to run CF on? I can switch them around and run either pi
We have two servers to choose from for loading CF. One is a current CF
webserver, the other is a new webserver that will be used for MySQL
databases. My dilema is, since I have the option now, which one do I want
to run CF on? I can switch them around and run either piece on either
server.
Th
5 matches
Mail list logo