Matrix 4.2.1 backend is very slow

(Simon) #1

I've recently upgraded my installation to 4.2.1 and creating/ committing is taking many minutes. Previously it was almost instant as expected.


There is nothing strange being reported in the system log or error log.



Is there anything I can check??



Thanks.

(Edison Wang) #2

This is a very difficult question to answer because of lack of information. Slowness can be caused by too many things.


which version are you upgrading from? Do you experience slow all the time or just peak hour? Did change any server settings?

Do you have any helpful information? Do you have a xdebug cachegrind profile?

(Rhulse) #3

[quote]
I’ve recently upgraded my installation to 4.2.1 and creating/ committing is taking many minutes. Previously it was almost instant as expected.



There is nothing strange being reported in the system log or error log.



Is there anything I can check??



Thanks.

[/quote]



You reported a very slow front end in this other thread.



You probably have something major wrong with your system.

(Simon) #4

[quote]
You reported a very slow front end in this other thread.



You probably have something major wrong with your system.

[/quote]



Yes that was an independent problem.



I resolved the issue. After analysing the system.log the longest step was creating the asset. Disabling Rollback fixed the problem.



Thanks all for your suggestions.

(Tbaatar) #5

I find that Matrix backend is almost unusable with Firefox 4. You can't drag asset and the drag and pop does not work, also the interface flickers a lot.

(Edison Wang) #6

[quote]
I find that Matrix backend is almost unusable with Firefox 4. You can't drag asset and the drag and pop does not work, also the interface flickers a lot.

[/quote]





You are using mac right? I got this bug report open on bug tracker.



http://bugs.matrix.squiz.net/view_bug.php?bug_id=5030





I'm suspecting it's a problem with Apple's Java Plugin for NPAPI browsers.

(Tbaatar) #7

Yep, I'm on Mac.


Thanks for pointing out the bug.

(Edison Wang) #8

Just an update on this.


Those two issues with asset map applet ( reversed tab text, drag and drop fail)



are now confirmed by Apple. It is duplicate to other people's bug reports:



Duplicate/8598522

Duplicate/8790184

(Tbaatar) #9

Thanks for the update.


So does this mean the problem won't be fixed until Apple sort the Java Applet?





Another bug I found is the magnifying/search glass next to an asset ID to find the asset in the tree does not work.

(Benjamin Pearson) #10

[quote]
Thanks for the update.



So does this mean the problem won't be fixed until Apple sort the Java Applet?





Another bug I found is the magnifying/search glass next to an asset ID to find the asset in the tree does not work.

[/quote]



If you cannot use the magnifying glass, it might be a problem in the database table (more specifically the sort order on the link table is out of sequence), to find out if this is the problem try running the system check script and look for the broken sort order test.



HTH

(Edison Wang) #11

We will wait for next release of Apple's java. If they are not planing to resolve it, we will have to find workaround.
Drag and drop is a big issue, it's pretty hard to find workaournd.





Apple fixed the binocular problem in latest Java version, check it out.

We have also placed workaround in latest Matrix:

http://bugs.matrix.squiz.net/view_bug.php?bug_id=5001

(Andrew Palmer) #12

Does anyone know if there are still ongoing issues with accessing the EES and backend from Macs?
Using either Safari or FF I'm waiting 25-30 seconds for a page to load.

(Nic Hubbard) #13

[quote]
Does anyone know if there are still ongoing issues with accessing the EES and backend from Macs?

Using either Safari or FF I'm waiting 25-30 seconds for a page to load.

[/quote]



I have been using Matrix on a Mac for about 5 years and have not had any problems.

(Edison Wang) #14

If the performance issue affects both EES and backend, it's not likely to be the problem of Matrix code.
It could be some implementation, for example, a listing page lists thousands of assets, or a listing page lists nested sets of listing pages.

Or it could be simply your network/hardware problem.



You have to have sysadmin or Squiz Support to have this issue looked.