If you have enough data or insert volume that you can reasonably use
dedicated hardware, you should probably use that.
(http://spyced.blogspot.com/2010/03/why-your-data-may-not-belong-in-cloud.html)
If you don't, then having CL + data on the same volume isn't going to
hurt nearly as much as sharin
On 03/25/2010 11:18 AM, Ethan Rowe wrote:
[snip]
I'll defer to the Rackspace folks regarding Rackspace Cloud; it has
been I/O on average since you're dealing with a real, local disk. But
I don't know about getting a second disk in that environment, though.
That should have said "better I/O o
On 03/25/2010 11:10 AM, Mark Greene wrote:
The FAQ page makes mention of using separate disks for the commit log
and data directory. How would one go about achieving this in a cloud
deployment such as Rackspace cloud servers or EC2 EBS? Or is it
just preferred to use dedicated hardware to get t
The FAQ page makes mention of using separate disks for the commit log and
data directory. How would one go about achieving this in a cloud deployment
such as Rackspace cloud servers or EC2 EBS? Or is it just preferred to use
dedicated hardware to get the optimal performance?
Thanks In Advance!
Be
