Redmine

The nested set model for Redmine issues is scoped under each root. So adding a subtask updates the issues that are under the same root only, not all issues. 1192 subtasks under a same parent is not a common situation, I'll try to reproduce but I'd really like to see the whole log in debug mode to see what is happening.

Right, I did forget about the scoping under the root issue.
I have attached the log showing 3 operations: show the issue details, show new subtask form and POST request. It is captured on different machine so the timings may be a bit different.
I could not find a single SQL request that takes such long time. It seems that it is a sum of huge number of individual requests.

It seems that since I was testing it the number of subtasks has grown, there is now 3696 issues orginized in a tree with 4 levels of depth where most of them are on 1 & 2. There is 87 project members.

mysql> select count(1) from issues where root_id=4821;
+----------+
| count(1) |
+----------+
|     3696 |
+----------+
1 row in set (0.00 sec)

mysql> select count(1) as count, (SELECT (COUNT(parents.id) - 1) FROM issues AS parents WHERE issues.lft BETWEEN parents.lft AND parents.rgt AND issues.root_id
= parents.root_id) as depth from issues where issues.root_id=4821 group by depth;
+-------+-------+
| count | depth |
+-------+-------+
|     1 |     0 |
|  1837 |     1 |
|  1558 |     2 |
|   300 |     3 |
+-------+-------+
4 rows in set (13.74 sec)

mysql> select count(1) from members inner join projects on projects.id=members.project_id inner join issues on issues.project_id=projects.id where issues.id=482
1;
+----------+
| count(1) |
+----------+
|       87 |
+----------+
1 row in set (0.00 sec)

The table agile_colors is from RedmineCRM Agile plugin. It could have some impact on "show" but it should not have impact on "new". The "new" is most painful as it takes minutes.

I have removed all plugins and run it, this is how long adding subtask took (full log attached):

Completed 302 Found in 93976ms (ActiveRecord: 85036.7ms)

Thanks for the feedback. I was able to reproduce this behaviour with Redmine 3.0 and Redmine 3.2 as well, this is due to thousands of queries on issues and issue_relations tables. The good news is that this problem is fixed in 3.3 (by this commit: r15056). Here are the results on my machine with an issue that has 3200 subtasks on 3 levels:

Redmine 3.0 / 3.2 (this could be dramatically slower depending on the database):

Completed 302 Found in 12210ms (ActiveRecord: 4093.2ms)

Redmine 3.3 with the same data:

Completed 302 Found in 353ms (ActiveRecord: 61.0ms)

Showing the issue details with all its subtasks is still a bit slow (2 ou 3 seconds) but we can't make the rendering of thousands of links much faster. We should probably limit the number of subtasks that are displayed on the issue details and add a link to the issue list with a filter on parent issue to show a paginated list of the subtasks.

I'm closing it as it seems to be fixed, please reopen if you're still experiencing problems after upgrading.