[foxboro] Off Mesh Galaxy database
- From: stan <stanb@xxxxxxxxx>
- To: Foxboro List <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 24 Mar 2010 07:55:05 -0500
Has anyone implemented a design where their Galaxy DB is "off mesh"?
What I am referring to here is a design where IEEE is on an AW on the mesh,
and has it's database located on a machine connected to this AW via an
additional NIC.
To kind of explain why I am thinking about this here is the long version.
It is my understanding that to be "on mesh" any machine must run only a
single core, even if it is for instance a quad core machine. If this is
incorrect, I would love to hear that, BTW. So, given the perceived fragility
of this DB, I am thinking that, particularly when we are doing active
development work, we want to back up this DB _very_ frequently. Now I would
like to minimize the amount of time spent doing these backups, and it seems
to me being able to run this on a machine that I can take full advantage of
the power of the hardware would be advantageous.
Thoughts?
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
- » [foxboro] Off Mesh Galaxy database - stan
