[TYPO3-dev] Workspace trouble in TYPO3 4.5

[Christian Lerrahn]

Hi
On Sat, 13 Aug 2011 03:06:53 +1000
Christian Lerrahn <typo3 at penpal4u.net> wrote:
> I think I might have demystified this problem. It seems that the
> Workspaces module eats up a lot of memory. So, while the BE and FE run
> fine with the memory I'd allocated to PHP, I needed to increase the
> memory to get the workspaces to work at all times (they did work
> erratically). As my PHP install had not been logging errors before, I
> couldn't tell what was happening until I started playing around with
> settings.

I might have got a ahead of myself there a bit. :( As it turns out,
everything only worked for a little bit and then the same problem
re-occurred. In fact, even raising the memory limit further did not
make any difference. :(

I've now had a look at the traffic and found that the server really
sends incomplete replies. The JSON reply has a content length which is
longer than what is sent (I found one reply to be about 800 bytes when
it was supposed to be about 1300 bytes). Several of these are all cut
off at the same point reading

... t3-icon-x-content-text","icon_Workspace":"t3-i

There is often even another reply on the same connection which has the
same problem, i.e. the next HTTP response follows directly after the cut
off part. Obviously, these arrays are incomplete and thus useless which
is probably why I see a connection error.

The problem I have is even with really extensive logging, I can't find
anything in TYPO3 log, Apache logs, MySQL logs, syslog (includes PHP) or
kernel logs. There is just no trace of anything going wrong.

The time outs are set to 900s to eliminate them as a reason.

The load sometimes goes up beyond 1 when testing. However, even when it
doesn't this still happens.

Oh, and I have had this problem with the same site on different servers
running different OSs.

Any suggestions what might be happening here? Who is the culprit? TYPO3?
Apache? PHP? How do I debug this?

Why is the content length correct but the content cut off?

Cheers,
Christian

> On Sat, 25 Jun 2011 17:40:38 +1000
> Christian Lerrahn <typo3 at penpal4u.net> wrote:
> 
> > Hi,
> > Part of this is probably more of a bug report. However, I cannot
> > really tell what is happening, so a bug report would be rather
> > useless at this stage. Instead, I'd like to get some opinions here
> > and then investigate further.
> > 
> > First of all, I'm under the impression that the workspaces in 4.5
> > are much more resource hungry than they were in 4.4. The AJAX calls
> > performed when listing changes, are putting my single core server
> > under heavy load. Just one such listing on a small tree will drive
> > up the server load to ~10 for a significant amount of time. This
> > seems unacceptable and I'm wondering if there is a bug somewhere.
> > 
> > Furthermore, I have a couple of pages which have only one content
> > element each. When I look at the histories in a draft workspace and
> > the live workspace, I can see that there are unpublished changes.
> > However, selecting these pages in the workspace module will only
> > yield a never-ending search while keeping the server under heavy
> > load. I'd just publish these changes blindly (which it isn't really
> > anyway because of the history) but there doesn't seem to be any way
> > (other than manipulating the database). What could be going wrong
> > here? The records look as follows
> > 
> > uid 	pid 	t3ver_oid 	t3ver_id
> > t3ver_wsid t3ver_label 	t3ver_state 	t3ver_stage
> > t3ver_count 	t3ver_tstamp 	t3_origuid 8191
> > 4433 0 		1 		0 		First
> > draft version 	0 	0 		0
> > 1307694521 	0 8225 	-1 	8191 		2
> > 		2 		Auto-created for WS #2 	0
> > 	0 		0 		0 		8191
> > 	
> > 
> > Any suggestions why the workspace module might not like those?
> > 
> > Cheers,
> > Christian
>