Bug #36744

Workspaces are unusable on larger installations

Added by Bart Veldhuizen over 9 years ago. Updated 8 months ago.

Status:
Accepted
Priority:
Should have
Assignee:
Category:
Workspaces
Target version:
-
Start date:
2012-08-12
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
TYPO3 Version:
4.5
PHP Version:
5.2
Tags:
large-site,usability
Complexity:
Is Regression:
Sprint Focus:

Description

We're running TYPO3 4.5.12 on a website with a few thousand pages. Opening the workspace module on the root page of this site doesn't work - it creates a huge load on the server and in the end the page fails to load. Doing this with several users at once kills our server.

This is a big problem for us and we're willing to sponsor this with a serious budget.


Subtasks

Bug #39727: Calculating percentage of differences is slowRejectedOliver Hader2012-08-12

Actions
Task #39728: Optimize runtime on objects and database queries ClosedOliver Hader2012-08-12

Actions
Feature #39729: Allow to disable Extbase TypoScript parsing in backendRejectedOliver Hader2012-08-12

Actions
Bug #39731: Calculate percentage of differences if column is shownClosedOliver Hader2012-08-12

Actions

Related issues

Related to TYPO3 Core - Epic #93547: Collection of problems with large sitesAccepted2021-02-19

Actions
#1

Updated by Oliver Hader over 9 years ago

Thanks for your report and the sponsoring offer. If we create a code-sprint for performance on the workspaces part out of it, it might take a bit longer (since the sprint won't start tomorrow, but maybe in one or two months). So, maybe sponsoring an individual developer might make more sense in that regard...

The current implementation has three problems:
  • huge amount of queries for all tables and pages
  • caching issues if the result set exceeds the available (database) cache space
  • sorting elements (depending on the selected column in the module) happens always (uncached)

I think a lot can be done on the query part.

#2

Updated by Bart Veldhuizen about 9 years ago

When you say 'sponsoring an individual developer', is that something the workspaces team can help me with? I don't think I would be able to find a developer that could do this for me as this is such a highly specialized piece of code.

#3

Updated by Oliver Hader about 9 years ago

  • Assignee set to Oliver Hader
#4

Updated by Oliver Hader about 9 years ago

  • Status changed from New to Accepted
#5

Updated by Herbert Sojnik almost 9 years ago

We have at least one customer with the same problems, therefore we are interested in co-sponsoring a performance tuning.

But one important question before:
What is the roadmap for workspaces & version in generell?
Will the actual implementation (we use TYPO3 4.5) be obsolete by April 2014?

#6

Updated by Bart Veldhuizen almost 9 years ago

We have sponsored the development of this module and Oliver Hader implemented it for us. The resulting improvement in performance is amazing.

@Oliver: could you please release this module on TER so Herbert can use it as well?

Thanks!

Bart

#7

Updated by Oliver Hader over 8 years ago

Bart Veldhuizen wrote:

We have sponsored the development of this module and Oliver Hader implemented it for us. The resulting improvement in performance is amazing.

@Oliver: could you please release this module on TER so Herbert can use it as well?

Thanks!

Bart

You can clone the status from GitHub - the optimizations have been created for a TYPO3 4.5 website.
Those changes modify the behaviour of Extbase bootstrapping for the workspace backend module as well.

see https://github.com/ohader/workspaces_performance

Most of the changes already have been integrated into TYPO3 6.0.

#8

Updated by Herbert Sojnik over 8 years ago

Thanks Oliver for supplying your extension!

I tested it in my small test system and it worked correct.
Bbut within our large TYPO3 installation, that consists of about 13.000 pages, I always get a memory overflow.

I debugged our code and found the problem in the function findAll in the class Tx_WorkspacesPerformance_Utility_PageUtility:

All entries of the pages table with all columns are loaded by exec_SELECTgetRows and are kept in memory! I tried to reduce the columns from "*" to a few important ones (uid,pid,title) and could solve the problem.

Which columns are neccessary for the workspaces extension and should be loaded from database here?

#9

Updated by Michael Stucki over 7 years ago

  • Category changed from Code Cleanup to Workspaces
#10

Updated by Michael Stucki over 7 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
#11

Updated by Mathias Schreiber over 6 years ago

  • Target version set to 7.5
#12

Updated by Benni Mack almost 6 years ago

  • Target version changed from 7.5 to 7 LTS
#13

Updated by Mathias Schreiber almost 6 years ago

  • Target version deleted (7 LTS)
#14

Updated by Sybille Peters 8 months ago

  • Tags set to large-site,usability
#15

Updated by Sybille Peters 5 months ago

  • Related to Epic #93547: Collection of problems with large sites added

Also available in: Atom PDF