Hi,
When I install and configure the module the memory consuption explodes and my side goes down.
I'm running a druapl instance on a server with 256 MB of main memory, I have round about 500 Pages, and only some tags.
Do you have any experience with that, how much memory is needed? How big can sites get? Is there a linear memory increase? How many user / hour can the modul support before it get down.
Regards Christian

Comments

giorgio79’s picture

giorgio79 commented
Version: 6.x-2.7 » 6.x-2.8

+1

indytechcook’s picture

indytechcook commented
Status: Active » Postponed

+1

Oh wait. I'm working on this as part of the rewrite. The cache will be my friend.

andrewsuth’s picture

andrewsuth commented

+1

@indytechcook I would be really interesting in hearing your ideas of how to implement caching for this module. If you've already got some code I'd love to see it so we can share some ideas/code to get it up and running.

mbrighi’s picture

mbrighi commented

+ 1

indytechcook’s picture

indytechcook commented

A big help will be moving the configuration out of variables. Right now they are stored very ineffectively. A variable for each settings. I'm moving to an OO based methodology. There will be one record in one table that holds all of the configuration. The settings will be cached in a effective manner.

I also plan on caching a tid => tids/mlids and nid => tids/mlids relationship to know what records need to be updated without heavy querying of the db.

I don't have any code to share yet but I hope to within a month.

francula’s picture

francula commented

I had a fruther try and i think that the problem is the breadcrum thing.

eL’s picture

eL commented
Version: 6.x-2.8 » 6.x-2.9

Any news about this? I have two vocabs with circa 2500 terms and if menu Rebuild is done, VPS with 2 GB of RAM dies with run out of memory :(

eggersrj’s picture

eggersrj commented

Any udpates to this?

I'm running into the same problem -- every time taxonomy menu loads it crushes my server. The main vocab on my site has less than 600 terms...

bigsyke’s picture

bigsyke commented

Same here in D7, each page load even with minimal terms with the Tax menu enabled, averages around 3k-4k milliseconds. Disable the module and its down to 200ms avg.

johnv’s picture

johnv
Primary language Dutch
commented
Version: 6.x-2.9 » 7.x-2.x-dev

indytechcook is hinting on 'loading the taxonomy tree' as a performance problem.

My problem (with D7) is 'loading the terms' happens for every term in the menu. This isn't a memory problem (yet), but it is hurting the page response time, since the menu is being rebuilt on EVERY page request, and every 'term load' generates a db-request and extra calculations.
So, depending on the root cause, the following issue is either related or a duplicate:
#1973920: Memory/Performance problems, when building a menu with a large taxonomy_menu

vladimiraus’s picture

vladimiraus
Primary language English
Location Brisbane 🇦🇺
commented
Issue summary: View changes
Status: Postponed » Closed (outdated)

Thank you for your contributions.
Drupal 7 is no longer supported.
Closing this issue as outdated.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.