Opened 3 years ago

Closed 3 years ago

#11658 closed Bug/Something is broken (fixed)

Dev site on floriberto crazy slow, basically unusable

Reported by: https://id.mayfirst.org/rootwork Owned by:
Priority: High Component: Tech
Keywords: floriberto Cc:
Sensitive: no

Description

Hi folks,

I've been working on a development site at new.titaniumringsforever.com. It's a Drupal Commerce site, and I know that brings with it big memory issues. I think we'll probably move it off of MayFirst once we launch so that we get better performance and don't negatively impact other members, since this is a for-profit site.

However, in the meantime, I've been developing on my MayFirst account. I've been using this development site for months and months, and it's been fine.

All of a sudden, over the weekend things got dramatically worse. It often takes 1-2 minutes to load a node-edit page. Many times -- probably 25% of the time -- I get server capacity errors. I've tried upping the PHP memory just to see if that helped, and it did a little bit but it's still much much slower than it was before. I've tried clearing the cache and resetting the server (by editing the web config) and that will get me out of the server capacity error but things are still slow, and eventually I get the capacity error again.

And again, this is a dev site, so at most there are a grand total of two people visiting it. Yes, the caching and CSS/JS concatenation is off, and that makes page loads slower -- but that doesn't explain server capacity errors.

If Drupal Commerce is just too much for a shared account on MayFirst to reasonably handle, even with no traffic, then I'll accelerate our plan to move the site somewhere else for development in addition to launch. But since things have only recently and very dramatically slowed down, I thought something might be up on the server.

Thanks for your help!

--ivan

Change History (2)

comment:1 Changed 3 years ago by https://id.mayfirst.org/jamie

Hey Ivan - we started noticing these problems as well a few days ago. Last night Jaime identified a run-away process on the host which we have killed - I think we should start seeing much better performance today. Can you let us know how it goes?

comment:2 Changed 3 years ago by https://id.mayfirst.org/rootwork

  • Resolution set to fixed
  • Status changed from new to closed

Yep, things have been much better over the last couple of days. Thanks for taking care of this!

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.