| Project: | Menu Node Edit |
| Version: | 6.x-1.6 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Man ... I feel like all I do is ask questions on your modules and never help anyone. Hopefully I can change that soon.
Anyway, I'm starting to get worried about my site's reliance on this module--I think I'm going to end up with too many menu items. One look at Drupal's menu management interface can tell you that we are not expected to have hundreds and hundreds of things in there. But this module exists, basically, to give the Drupal menu more significance than it had ... and in my case everything is going to be routed through it.
In fact I'm using the section idea to break my site into around a dozen areas, each with a "guide" that is expected to produce new content regularly. They've been doing that for a few weeks and just as we're getting ready to launch, I'm starting to get WSODs on /admin/build/menu-customize/primary-links. PHP currently gets 64Mb and that ends up allowing for around 13 apaches on my server ... that is already cutting the default by a third, and I'm not thinking it's going to be good to start kicking that below 10. Plus it seems futile anyways ... that menu is only going to grow and my site's not even launched yet. If everything goes according to plan, I'll have a thousand items in that menu not too long from now.
WSODs on the menu-customize page is bad enough, but I'm starting to worry if an inflated menu is going to start having memory implications everywhere the menu is loaded. Not sure whether it would make a difference if the items are disabled, but it certainly doesn't on the menu-customize page; they show up there regardless.
So, put plainly, my question is this: How scalable do you think this module is, if someone puts a whole lot of nodes into it? If I double the RAM on the server and thereby get the ability to significantly boost my memory limit, is it likely I won't hit the ceiling again at some date in the future? I don't understand enough about the Drupal project to know how to make these kinds of judgements. Should I take steps to find out more about exactly where the memory is going?
Thanks in advance.
Chris
Comments
#1
I have some unreleased patches that help with this. But it's a problem.
If you have more than 1000 menu items, there are all kinds of UI and memory problems. One fix is to replace menu drop down forms with autocompletes.
Another is to paginate the menu over view page. Both of which we have code to do, just unreleased.
Even so, when menu rebuilds hit, you're looking at 160 MB + if you have a large menu.
#2
Using lots of small menus instead of one big one helps some, too.
#3
Thanks a ton, Ken.
The small menus idea is very intriguing ... and as I think about it, I'm only using the menus for this module's sake, and not actually to use as menus. So I could very possibly move all of my sections to separate menus and I'm thinking (hoping!) that it would make no difference anywhere.
It doesn't really change the problem, it's just delaying the inevitable--but in my case I'm delaying it by a factor of 12, and that's huge.
I'm going to give that a try, but I'd also love to know more about your fixes if/when you release them.
[not sure when the right time is to mark a question like this "fixed"]
Thanks again,
Chris
#4
I would leave it open. I have some experimental code that I mean to attach for you to test.
#5
This module, for instance, which turns Menu select lists into autocompletes, and really cuts memory usage when editing nodes.
#6
Thanks. I can't test anything experimental at the moment other than what I absolutely have to, and my problems seem to be solved for the moment. But when my test environment gets caught up, I'll make sure to give it a whirl.
#7
Oops . . . nothing to do with this module . . . this problem crops up with the core menu admin module.
@ Chris: I have a site that already hits the meagre memory limits imposed by a shared server environment . . . I can't use menu administration. I only have 380 nodes right now. The error popped up at about 350 nodes.
I get:
"Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 3060509 bytes) in /home/xxx/public_html/includes/common.inc on line 167"
on http://marcellaedmund.com
peace,
Grant