Posted by j0k3z on August 18, 2010 at 1:28am
I am running Mercury on Amazon EC2 with my mySQL running on an attached EBS volume. I am getting very bad performance though when doing certain queries, upwards of 7000ms when Ican run the same queries in 100ms on a crappy shared server. So I am either doing something wrong or maybe putting mysql on a volume is just a bad idea?
Comments
Does anyone have any
Does anyone have any comments?
Is a small instance with MySQL on EBS just a bad idea in general? Is there a recommended instance size for databases?
HUH? What? Small? For
HUH? What? Small? For low-traffic, small sites you can use a tiny (micro) instance. Depends on load/usage/needs. Otherwise there are PLENTY of FAQs out there-- google, man!
~kwt
If I am having trouble with
If I am having trouble with slow speed on a small instance then why would you even mention moving to a micro instance?
re: If I am having trouble with
I think he was suggesting that the size/traffic of the server largely dictates the server size you'll need.
I think he was also suggestion that many sites will run fine on a micro, indicating that unless your server is either very large or very busy, then yes, something is wrong on your server.
I suspect that AWS volume read/write speeds are variable based on traffic on the internal network and the load on the server that the volume is running on (not your server).
Hope this helps,
Greg
--
Greg Coit
Systems Administrator
http://www.chapterthree.com
Dear "Farang," We seem to be
Dear "Farang,"
We seem to be having some communications problems here.
First, might I suggest you might get better responses and be taken more seriously if you used a nick other that "jokers?" Just maybe? Such as your IRC nick-- which I would recognize :) ?
Your question wasn't answered the first time. There's a reason-- there are no dumb questions, but there are clueless ones, asked in the wrong place, in the wrong way.
As for the second time you asked, I will quote the immortal factoids of the Druplicon:
anybody?
If someone knows and cares, they'll respond. Silly or impossible questions will usually go without an answer. If you believe your question is sane, try again in a few hours or post to http://drupal.org/forum .
You've also been around long enough to know the social rules, and that pestering people to get attention will get a negative response, if any at all. This is not IRC; we all get the email and read it. And while your question is (arguably) sane...
Next, you're not bothering to be clear. Your subject line was "How do you setup your mysql on Amazon Ec2?", and your "follow-up" (really: "please pay attention to me!!!") question was:
Well, that's the question you got answered. Now you're being a jerk about the fact, that you got this question answered.
What do you expect? :)
In this case, if your subject line actually matched the question you wanted to ask, or the content of the message actually bothered to spend the time clarifying what you wanted, then, perhaps, someone would have given you an answer the first time--
~kwt
Wow, I didnt realize posting
Wow, I didnt realize posting additional details, or a follow up after 2 months without response was considered "pestering people" or -- "please pay attention to me!!!" Are you serious? Did you really need to respond to this thread?
"Now you're being a jerk about the fact, that you got this question answered."
You answered my question? I mentioned that I was having speed issues with a small instance and you told me to switch to Micro instance, how is that answering my question? Sure, there are other websites around the internet with details about Mysql on EC2, and I have checked many of them for months, but I want the Drupal perspective.
Are you just another internet tough guy policing the forums or do you have something of substance to contribute? Isn't this forum supposed to be a place where people can ask questions? I'm sorry I am not a Drupal or hosting expert like you
Here is some advice, if you dont have something to contribute then dont waste your time replying to threads. Besides, shouldnt you be fixing that fatal error on http://www.1kenthomas.com/