Basically the problem I have with the module is that it causes my site to stop responding as soon as someone hits logout. You can read the post at http://drupal.org/node/12909 near the end - comments by Lunas. I narrowed my problem down to this module. In a nutshell, with the module enabled, mysqld gets severely overloaded and causes the site to be unresponsive. As soon as I disable and empty the node-access table resetting to default drupal install everything fires back up. Suggestions?

Comments

ankur’s picture

ankur commented

Refreshing issue for 4.5 -> 4.6 port. If this is a bug, I'd like to fix it.

-Ankur

Angelo Bonadonna’s picture

Angelo Bonadonna commented
Title: Causes logout to hang » Causes MYSQL to overload and pages

I was wondering if there was any progress on this matter. Like Lunas (who refers to the thread I started at http://drupal.org/node/12909), I too have pinpointed my problems (which is the extremely slow loading of pages, with MYSQL becoming overloaded) to this module. (When I disable this module, the site works just fine.)

I've identified the problem as occurring only on a drupal installation that was an UPGRADE (from 4.4.2), not a fresh install (I have serveral "new" 4.5.2 Drupal installations that work just fine with this module.)

Does the problem have to do with something that happens in the MYSQL tables during the upgrade process? Is there any way for a novice to edit the MYSQL tables? Would an upgrade to 4.6.0 help? Thanks... --Angelo Bonadonna

ankur’s picture

ankur commented

I've heard this occassionally reported, but cannot really comment on what is going on here. I know that when the module is enabled on a site that already has a number of nodes, where also the node_privacy_byrole module hasn't been enabled before, there is the potential of a heavy MySQL CPU usage when you save "Enable" on q=admin/settings/node_privacy_byrole....

This is because the module is updating permissions for every node on the site in terms relevant to each node, rather than each node-type, meaning that a lot of database operating are going to take place...

This is something that would require some research and analysis at later time....

Will leave this open for now and try to come back to it at a later time...

-Ankur

degerrit’s picture

degerrit commented

I noticed this too, and it seems to affect some node types/blocks more than others, I guess depending on the query (if that's possible).

I've noticed several things: for every group, whether the group can edit or modify a node or not, a row is inserted into the database. I always wondered if it was really necessary to do that, since for my site for example (>15000 nodes and 6 roles) that results in a heck of a lot of rows.

Secondly, maybe it can be reduced even more: by only saving node permissions if they deviate from the default node permissions for a certain node type. I guess that would be tricky to implement though, especially if the default node permissions were to change...

jondoesdrupal’s picture

jondoesdrupal commented
Status: Active » Closed (fixed)

Tidying up old issues. Closing this one off as it relates to an obsolete version of Drupal.