Goodbye to eatj
22 March, 2008
Due to the library and memory requirements of my blog, I had to leave eatj.com this month for greener pastures. The 64MB limit their shared hosting plan provides (undocumented until you go over) is very hard to abide by even with the most basic app. This past month I had to purchase an additional BASIC plan to account for the peaks. It was nice while it lasted but it’s about time to move on. So I have to remove my recommendation for eatj.com as a production Grails hosting.
I’ve since moved to VPSLink.
I also use www.eatj.com and ran into the memory limitation. They are 1000% better then go-daddy who will not let you re-start Tomcat instead having to wait until approx 1 a.m. every day.
I agree though 64MB is not enough. With zero applications and just Tomcat running I think my eatj account clocks in at 40-42 MB so that doesn't leave you much to play with. I am using GSPs even for static content to take advantage of site mesh and the way GSPs let you use dynamic linking. Briefly considered using regular HTML for static stuff to save on RAM but this would incur painful maintenance when things change...
Have you ever played with the grails Cacheable plugin? It is based on the Java cache library ehcache. It was mentioned at the Future of Web Apps in Miami http://www.syrics.de/pages/page/show/43 I was going to investigate this to speed up load times on shared java hosting accounts (instead of reverting to static HTML)
It must be said that EAT-J support is excellent. They typically respond to email within 15 minutes, even weekends.