Project

General

Profile

Actions
Copy link

Task #54990

closed

Epic #55070: Workpackages

Epic #55065: WP: Overall System Performance (Backend and Frontend)

Story #55073: review autoloader and language cache

ClassLoader cache ist too slow, no matter which CF Backend is used

Added by Rupert Germann almost 11 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Performance
Target version:
6.2.0
Start date:
2014-01-14
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.4
Tags:
Complexity:
Sprint Focus:

Description

while Profiling a 6.2 installation with XHProf I found that the most expensive part of the request is always the classloader cache - no matter which CF backend is used for it.

the attached callgraphs both show the delivery of a cached page, one with the default configuration (simple file backend) and one with the classloader cache Backend set to memcached.

In both cases we see that either file_get_contents() or Memcach::get() is the most expensive function.

the request times (mesured with the adminPanel) are almost the same in both cases: ~155ms with simple file backend and 150 ms with memcache

Since memcache should be way faster than the filesystem I think there's a lot of room for optimizing in the classloader.

Files

Download all files
callgraph_filesystem.png (2.83 MB) callgraph_filesystem.png Rupert Germann, 2014-01-14 16:54
callgraph_memcached.png (2.23 MB) callgraph_memcached.png Rupert Germann, 2014-01-14 16:54

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #55029: Class Loader fails if entry in class cache is discardedClosed2014-01-15

Actions
Actions
Copy link

Also available in: Atom PDF