Project

General

Profile

Actions

Bug #75730

closed

Slow Backend because of node_modules folder

Added by Philipp Faber about 8 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2016-04-18
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I experienced a really strange behaviour of my TYPO3 setup. My Backend got really slow. I then deleted the typo3conf/ext/template/Resources/Private/Preprocessing/node_modules folder in my sitepackage that I need for pre-compiling my scss. Now backend speed is back to normal. This only happens on my production server (linux). On my local windows dev environment everything is great. I know technically on the production server folders things like `bower_components` and `node_modules` should be in .gitignore and not even on there.

Thoams Maroschik suggested the following:

I'm not sure whether it applies to TYPO3 but in Flow the Language service looked up the Resources folder for xlf files and traversed all folders/files. in case of node modules these are a lot


Files

setup.jpg (134 KB) setup.jpg Philipp Faber, 2016-04-18 12:16
Actions #1

Updated by Helmut Hummel about 8 years ago

  • Status changed from New to Needs Feedback

Can you provide a stripped down example extension, which slows down the backend of an otherwise blank TYPO3 installation?

Otherwise we cannot reproduce this issue.

Actions #2

Updated by Philipp Faber almost 8 years ago

It looks like it can also happen with my windows machine. I will try to create an example extension. I think Thoams Maroschik is on to something here.

Actions #3

Updated by Alexander Opitz over 7 years ago

What is the state of this issue?

Actions #4

Updated by Alexander Opitz about 7 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF