I hear you... So let me give this a try and see if things get any
better. Assuming both boxes are on the same network, do you see any
network latency cost involved?
-Dov
-Original Message-
From: Michael Dinowitz [mailto:[EMAIL PROTECTED]
Sent: Monday, December 20, 2004 9:26 AM
To:
This is how I'd do it.
The web server has 2 nic cards. The first is set to the external network
only and is used for traffic. The second is set to internal only and is used
to transfer data to the box from the SQL. This removes excess traffic from
the network. The 'net stuff' should be on it's
to cluster, I think
This is how I'd do it.
The web server has 2 nic cards. The first is set to the external network
only and is used for traffic. The second is set to internal only and is used
to transfer data to the box from the SQL. This removes excess traffic from
the network. The 'net stuff
I'm thinking about clustering I read some of the articles on this
(bpurcells, and others, etc) and I'm still a bit confused about which is
the best way for Entry Level / simple clustering.
Right now I have 1 CFMX6.1 Pro license and a single IIS box, sharing
MSSQL2K with CF over 2 1Ghz
You could do that with a crossover cable from the Web server to the DB
server, right? No need for extra switches or anything like that.
Yes, I'm sure you could. However, within these sorts of environments,
typically there's an internal network used for hosting databases and other
internal
It is better to have a SPoF with 99.8% uptime then 2 systems with
95% uptime each :-)
I'm not sure I'd agree with that, as long as only one system is down at
any given time!
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
!
-Dov
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Monday, December 20, 2004 10:08 AM
To: CF-Talk
Subject: RE: time to cluster, I think
I'm thinking about clustering I read some of the articles on this
(bpurcells, and others, etc) and I'm still a bit confused
Actually, I was suggesting to throw more ram at the machine and seperate the
webserver from the SQL. While I do like tight code and DB, it's not the
first thing to add; Ram is.
I have 5 levels of optimization:
1. Code
2. DB structure
3. Hardware
4. Network
5. Server settings
Code and DB take
8 matches
Mail list logo