So the last question put the following constraints on a virtualization design and implementation problem.
Let's Review:
The constraints were that you have performance issues due to storage latency.
You have no budget the ONLY things that you can leverage is the extra hardware from the virtualization project.
So the only solution that makes sense whether it's the best is not a question.
One (I stress) one of the workable solutions is to acutally put the latency sensitive application back on physical hardware until you can ensure the storage state. Now what I mean is you can still keep it a VM but you toss it on a dedicated box with ESXi (no cost). Then using the local storage options that you have open to you create the least latency and fastest sub-system that you can.
Do you agree? Is there a solution that you think might work just as well?
Let me know. That is what the comment section is for :).
Talk to you guys soon.
Let's Review:
The constraints were that you have performance issues due to storage latency.
You have no budget the ONLY things that you can leverage is the extra hardware from the virtualization project.
So the only solution that makes sense whether it's the best is not a question.
One (I stress) one of the workable solutions is to acutally put the latency sensitive application back on physical hardware until you can ensure the storage state. Now what I mean is you can still keep it a VM but you toss it on a dedicated box with ESXi (no cost). Then using the local storage options that you have open to you create the least latency and fastest sub-system that you can.
Do you agree? Is there a solution that you think might work just as well?
Let me know. That is what the comment section is for :).
Talk to you guys soon.
1 comment:
I think that sounds pretty reasonable.
Post a Comment