Loading Profile...
EMPLOYEE
Problems with your EY account?
tomstuart
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
Hi Jason,
I'll ping Ed and find out where things are with this. My gut feeling is that it might have taken a back burner to some other systems engineering tasks that we've had to tackle, but I'm waiting to get the official update from Ed.
The company says
this answers the question
-
Inappropriate?Hi Tom,
Can you tell me a little more about the problems you're having with Engine Yard? We want to figure out how to help. -
Inappropriate?Hi Randall,
Firstly, I'm just blowing off steam, which is what Twitter is mostly useful for.
Secondly, it's frustrating that the Engine Yard slices feel so underpowered for the money, and in particular it seems unfair that applications use so much more memory on a 64-bit Engine Yard slice than on a much cheaper 32-bit development server, and yet the only solution is to pay for more RAM.
The "back and forth" consists of us saying "our application doesn't consume this much RAM on our dev servers" and Engine Yard saying "pay for more slice RAM, then" -- not so much a breakdown in communications as a mismatch of expectations, since we (unreasonably) just want things to be magically better.
I'm not sure there's much anyone can do about this -- it's largely a Ruby/Rails problem, at least while EY standardises on a memory-inefficient mongrel-cluster-on-64-bit-MRI architecture. Maybe in a year's time it really will be something magically better (YARV? Rubinius? mod_rails? other?), and everything will be peachy, but until then there's going to be steam that occasionally needs blowing off.
Cheers,
-Tom2 Comments Add a comment
This answers the question
-
Hi Tom,
I certainly understand the blowing off steam concept. We really do take how happy you are with your slices and our service pretty seriously.
I just read through the ticket history on this one. I'm getting in touch with Mutwin and Chris (the engineers who did the bleak house/memory leak detection work on the slices) We're going to see if we can find a solution to the memory needs for your application. Can't hurt to try at least once more. We'll update the ticket when we come up with something.
Sorry to hear that you're frustrated.
Regards,
-- Randall -
We're looking at a couple of different solutions, more memory being the low end. *No promises* but we might be able to have a 32bit VM with a 64bit kernel - would you be up for helping us test this if we can get it working?
Regards,
-- Randall -
Inappropriate?Tom:
Nice to hear another EY customer having the same problem as us. We have had about 5 separate "back and forths" with EY regarding memory and for a while we thought we were just being naive with memory.
Tom or Randall: Any progress with using a 32-bit VM with the 64bit kernel? Our company might be interested with this setup if it works well.
Regards,
Jason Yuen
Nulogy Corporation
I’m hopeful
-
Inappropriate?Hi Jason,
I'll ping Ed and find out where things are with this. My gut feeling is that it might have taken a back burner to some other systems engineering tasks that we've had to tackle, but I'm waiting to get the official update from Ed.
The company says
this answers the question
