托管提供商中的 Drupal 执行内存限制
我们开发了基于 Drupal 的门户。经过测试和部署（在本地）后，该站点运行良好。但是当我将站点移动到在线服务器（托管）时，该站点面临内存执行限制问题。
预计至少 96MB，但托管提供商无法增加那么多！还有其他方法可以解决这个问题吗？或者在澳大利亚有其他托管提供商提供这么大的内存限制吗？
We developed the Drupal based portal. After the testing and deployment (in locally) the site was working perfectly. But when I move the site to the online server (hosting), the site was facing the memory execution limit problem.
It's expecting minimum 96MB but the hosting provider is not able to increase that much!! Is any other way to fix this issue?? Or in Australia any other hosting provider is giving this much memory limit?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
根据我的经验，96MB 对于 Drupal 站点来说是很大的需求。查看您在网站上安装的模块并禁用和卸载您实际上不需要的任何内容。例如，如果您不使用核心颜色和注释模块（在 Drupal 6 中默认启用），请禁用它们。如果您安装了 Views UI、Beautytips UI、ImageCache UI 或 Rules Administration UI 等模块，请在完成所有配置后禁用它们。
如果只有特定页面需要过多内存，请尝试优化这些页面。例如，如果视图中显示大量节点，请尝试向视图添加分页器，以将内容拆分为多个页面。
如果您有自定义模块，请尝试将管理 UI 代码分离到单独的 modulename.admin.inc 文件中，以便仅在需要时才加载它。哎呀，考虑对公共贡献的模块也这样做，然后考虑将补丁发布到这些模块的问题队列中。
更新：接下来您可能需要考虑 VPS 托管。在那里，您将对正在运行的系统有更多的控制权。
更新 2：根据站点的需求和功能，您可以通过安装 Boost 模块，用于创建网站的平面文件版本。
In my experience, 96MB is a lot for a Drupal site to require. Look over the modules you have installed on the site and disable and uninstall anything you don't actually need. For example, disable the core Color and Comment modules (enabled by default in Drupal 6), if you're not using them. If you have module like Views UI, Beautytips UI, ImageCache UI, or Rules Administration UI intalled, disable them once you're done configuring everything.
If there are only specific pages that are requiring too much memory, try optimizing those pages. For example, if there are lots of nodes being displayed in a view, try adding a pager to the view, to split the content across multiple pages.
If you have custom modules, try separating out the administrative UI code into a separate modulename.admin.inc file, so it will only be loaded when needed. Heck, consider doing that for publicly contributed modules too, then consider posting patches to the issue queues of those modules.
UPDATE: You may want to consider VPS hosting next. There you'll have more control over the system you're running on.
UPDATE 2: Depending on the needs and features of your site, you may be able to reduce your site's memory footprint by installing the Boost module, which creates a flat-file version of your site.