Looking for some feedback. I've been with greengeeks for a while now and have been pretty happy (save for a definite pattern with the tech team not reading basic information every time that I submitted ticket) until today when I submitted a ticket because I can't access the permissions page...

We are still building the website and don't have any traffic really but after several hours of back-and-forth, I finally got a straight answer from a level 2 Tech person who told me that I basically would need to purchase a Premium plan in order to access the permissions page because it's too much for their servers.

Does that make any sense on a site that has no traffic? Our website is pretty intense - lots of custom coading and loads of modules but still... I can't even view the permissions page and I need to purchase a Premium plan to do so? Am I off-base thinking that this isn't right?

Comments

pixelsweatshop’s picture

They are right. Drupal is very ram intensive. The modules and permission pages probably the most. If you have a lot of modules with lots of permissions or a lot of roles those pages can take a lot to run. Drupal does not perform well on shared hosting and a vps or even a dedicated server is almost always needed.

sprite’s picture

Drupal is somewhat server resource intensive.

You need a server environment where you can configure PHP to a high resource consumption level.

A fully loaded Drupal (7 or 8) installation can comprise 30,000+ files and occupy 350+MB of disk space on server.

Also, even with properly configured opcode caching and so forth, server SSD storage dramatically improves server performance.

Drupal needs a hosting server environment that is specifically able to meet Drupal's resource needs.
Your host must:

- give you access to edit php.ini and increase memory limits and script execution time limits.
- provide a PHP environment with all necessary packages compiled in for good Drupal support, even minor items like exif.
- provide SSH CLI access and appropriate permissions to run: drush, composer, drupal console.

-----
Greengeeks ...

https://www.yelp.com/biz/greengeeks-santa-monica-2?sort_by=rating_asc

https://www.google.com/search?q=greengeeks+problems

spritefully yours
Technical assistance provided to the Drupal community on my own time ...
Thank yous appreciated ...

JoshDargie’s picture

Bryond1,

As the Operations Manager for GreenGeeks, it saddens me to hear customers indicate that they are unsatisfied with our services.

I have asked our Support Manager to review our front line support to correct any deficiencies related fully reading a ticket before responding. I fully expect that these sort of problems will be resolved in short order!

Regarding your concerns related to your most recent inquiry, I can certainly understand the frustration and shock being told an upgrade is required in order to utilize Drupal. Unfortunately, however, as some of the other commenters have mentioned some aspects of Drupal are extremely taxing as the product has grown in complexity over the years. It's for this reason we typically recommend customers utilizing Drupal purchase/upgrade to our EcoSite Pro or EcoSite Premium product lines which provide additional resources (CPU, Memory, Disk I/O) over our standard EcoSite Starter plan.

Unfortunately, without any specific details, I am unable to review your account and comment further on your specific situation. If you can send me a private message with your Main Domain or Ticket ID I'd be more than happy to investigate and make sure you are being looked after. At the end of the day, we want to see your problems resolved and you back to growing your business.

Finally, I would like to just bring attention to a recent upgrade to our product line - Scalable Hosting. With this new feature, customers are able to remain on our smaller plans longer by simply upgrading certain resources such as Memory or Disk I/O. These scalable upgrades can allow a customer to add and remove resources as demand dictates without the hassle of migrating servers or packages. It's possible that this may be all that is required to solve your issues :).

You can learn more about our Scalable Hosting improvements at: https://www.greengeeks.com/blog/2017/05/10/our-scalable-hosting-platform/

mmjvb’s picture

Hopefully you can set them in .htaccess.
See https://www.drupal.org/node/1565704 for suggested settings.

The above assumes the issue is caused by the number of fields to be handled on Permissions. You might want to use Edit permissions on the Role.