Permalink

From comment #1 :

- Performance; we haven’t worked on yet as we’re focused on architectural changes

Yeah, well there's your problem. You can't expect your architectural changes to perform well if you aren't considering performance when you are making those changes. That's the problem with Magento 1.

I'm 1.5 years into taking over a "new" magento site that cost the non-tech client $40k just prior to me taking it. It was so poorly implemented that half the features didn't work. I have written large PHP projects including information management for state universities, but this was my first magento experience. Super steep learning curve. A bear to manage code having to hop around directory trees 8-10+ levels deep and trying to figure out which price.html is actually putting the code out..

While I have cleaned up a lot of the issues they were having, we are still plagued with very slow TTFB, even on a dedicated SSD VPS (one site, very little traffic). The autocomplete search is useless as it would be 2 seconds before a response would come up. After some testing where I commented out the actual search part so it immediately returned no resuts, it only improved 100ms, so to me the slowness is just due to the time it takes to load magento's core...which is why every page has >1 second TTFB. I wrote my own search handler for the ajax query outside of magento (gasp!) and it responds in under 50ms.

Yeah I would never recommend Magento. It's a bloated slob. My $0.02 (US) :)

The content of this field is kept private and will not be shown publicly.

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
CAPTCHA
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.