Feeling Lucky
?
[#12552] - Saving new Article on large category
- Closed
- 28 Dec 2017
- Low
- Build: master
- # 12552
Steps to reproduce the issue
Creat an new article on a category with 1000s or more articles, first saving time takes about 10 sec.
Expected result
2-3 sec for saving an article. It was fixed on j3.6.1 (or 3.6.2, don't remember) but now it's back.
Actual result
System information (as much as possible)
j3.6.4 php 5.x on NGINX server
Additional comments
Votes
# of Users Experiencing Issue
0/1
Average Importance Score
3.00
franz-wohlkoenig
- comment
- 5 Apr 2017
@ch2856 ist this Issue solved?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12552.
| Status | New | ⇒ | Information Required |
ch2856
- comment
- 5 Apr 2017
Nope, it's not solved yet. It takes about 30 second to save an article. I solved it with saving to other category and then save it again to the right one.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12552.
| Priority | Medium | ⇒ | Low |
| Status | Information Required | ⇒ | Needs Review |
franz-wohlkoenig
- comment
- 6 Apr 2017
thanks for Info. Set Status "Needs Review" on Issue Tracker.
Quy
- comment
- 28 Dec 2017
@franz-wohlkoenig Close due to no response?
| Status | Needs Review | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-12-28 05:45:21 |
| Closed_By | ⇒ | Quy |
| Closed_By | Quy | ⇒ | joomla-cms-bot |
joomla-cms-bot
- comment
- 28 Dec 2017
Set to "closed" on behalf of @Quy by The JTracker Application at issues.joomla.org/joomla-cms/12552
Quy
- comment
- 28 Dec 2017
Closed as stated and no followup response by OP.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12552.
This was discussed here: #10567 Save new article (create a new ID) very slow in category with many articles
A patch was made to use last ordering: #8576 Performance gain - new featured article
Then it was reverted here: #11581 Revert "Performance gain - new featured article"
The revert was supposed (?) to be made together with a performance fix like for example this one:
#11184 Reorder tables with single SQL query (all DBs compatible), greatly improving reorder performance
(other performance fixes (PRs) were proposed too)
But only a revert was made in J3.6.3+ without adding any fix for JTable::reorder()