I've got a huge taxonomy with about 20.000 terms and four hierarchical levels. This taxonomy is associated to a CCK content type.
When I try to save a node belonging to this content typ, this action takes very long (on my local test server several minutes). On my life-server I get the message:
User warning: Lost connection to MySQL server during query query: SELECT * FROM users u WHERE LOWER(name) = LOWER('admin') in /home/www/Travunity/includes/database.mysql.inc on line 172.
I suppose, the saving-action takes a huge amout of time. But I can't understand this, because I'm assuming, that there is only an intex to tte taxonomy, witch needs to be saved. So, what takes such an amount of time??
I already raised max_execution_time to 180 and memory_limit to 70M.
Is there anything I can do?
Comments
Comment #1
ricabrantes commentedNo activity, Closed
Comment #2
smitty commentedI think this is a serious issue. You shouldn't close it without an answer.
Can you explain, what is going on there?
Comment #3
smitty commentedRe-opened
Comment #4
ainigma32 commentedIn case this problem still exists and you still want to find the solution I would suggest installing the Devel module. You can then log the queries that are executed. Post the query that is taking up all this time and we'll take it from there.
If this has already been solved please close this issue.
- Arie
Comment #5
catchHow many users do you have?
Comment #6
smitty commented@ainigma32: I am still interested in this problem. But at the moment I don't have the time to do the testing. So I'll do it later.
@catch: At the moment less then 20 users, but growing.
Comment #7
ainigma32 commentedThis thread http://drupal.org/node/227445 might be of some help.
Please post back if any of those solutions work for you.
- Arie
Comment #8
ainigma32 commented@smitty: Did you manage to find some time to look at this?
- Arie
Comment #9
smitty commentedSorry, this is a huge amount of possible sources and solutions. Because I am verry busy in other tings at the moment I have to postpone the testing.
But thank you very much for the Link. I'll check it later.
Comment #10
ainigma32 commentedI know the feeling. Hope you figure it out when you get around to it.
- Arie
Comment #11
tr commentedDrupal 5 is no longer supported. If you experience this problem in Drupal 6 or higher and can provide some steps to reproduce the error, please open a new issue.