Slow queries on large website

[breto33]

@garyjaybrooks again you are not addressing the real issue - Jupgrade IS NOT JOOMLA. Joomla should be providing the upgrade for their own software not a 3rd party. As far as paying for a commercial upgrade, this website is a state agency website. I don't know if you have been living under a rock or not, but budgets for most states in the US have been frozen for a couple of years.

And the unrealistic manual upgrade you propose still doesnt address the assets table. Do any of you guys work on sites larger than 10 pages? Your condescending responses assuming it is easy to get money or throw tons of hours at a problem (by a department that is already insanely understaffed) created by our CMS are getting old.

At least now we are past putting the blame on our servers and connections I guess thats one positive step.

[garyjaybrooks]

If you wanted the upgrade software built from 1.5 to >>> 1.6,1.7,2.5 - You could have volunteered yourself to build the code and donated 500 hours of your own time to donate it to the Joomla project. Nobody told you to move to new version of Joomla. You wanted to do it for a a reason or you felt it was the right thing to do. 1.0 to 1.5 was a major release just as 1.5 to 1.6 and above. Migration of content is not easy and takes a little love. In the case of using Jupgrade you are not so lucky in the world of free software. Just like if you were using Windows computer. If your on Windows 98 and you want a program to work in Vista you have to do your diligence and testing or buy the next version of software. If your a business you don't just jump to the latest and greatest and you make sure you have resources free to deal with issues that could happen. We are a volunteer project. The project worked with many upgrade extensions and they were provided as a 3rd party option. The Jupgrade people made a mistake, its to bad that it happened but it is the world we live in. Software is not perfect all the time. roll with the punches and invest your time to fix it.

Bret, it's even worse that you say that your with a gov and you do not have €24.95 to spend on helping the future of your own job. If I were in your position I would pull it out of my own pocket and talk to my boss about it.

I personally run a company with plus 50,000 Joomla sites and it's quite rude of you to poke at me for not fixing your problem for free.

Manually upgrading a site it not out of scope. If you need help and have very low budget you can always look for a $10.00 hour coder from http://www.odesk.com. Many coders in the world understand how to move data from 1 db to another.

Just because Joomla is free does not mean that everything you do in and around the area of Joomla is free. In many cases you have to invest into humans helping you, and in your case if your not a programmer then spending €24.95 is a great bet.

That all being said.. out of the kindness of our hearts, in Joomla land we are working on a good migration script. You could see it in the next few months.

Best of luck everyone.

[cuteschweinchen]

well said garyjaybrooks!!

[breto33]

@garyjaybrooks

Thanks

I will let anyone I know still on Joomla in a few months you might have a migration script for them.

[miracle3736]

So it seems the problem is in Jupgrade? Strange, I didn't use Jupgrade in the sites I have the problem with. I started with an empty 1.7 installation and used freakoud Content Uploader to get the content of my old sites (about 10K of articles) imported. This worked well. After some thorough testing we put the site live around the 20st of December 2011. Joomla 2.5 was released around January 24th 2012. So our site was up and running without any big problems for already a month. Some days after the release I upgraded to 2.5 and some days later all the trouble started.

So as far as I can see Jupgrade isn't the (only) problem.

[garyjaybrooks]

@Miracle3736 You will need to look at your assets table and see if you have a issue. If you do not have the assets table issue then we need to move up the line and figure out your issue. I suggest you open a brand new thread with your full problem laid out with screen shots of the assets table. If its not a assets table issue then we need to look at other issues up the line.

[miracle3736]

@Garyjaybrooks: I have looked at the assets table using the Wiki mentioned in this thread and as far as I can see it looks perfect. I can send it to you if you want. So I guess the assets table is not the problem. But what is the problem? Hope you can help me...

[garyjaybrooks]

Open a new thread with your details. We do not want to continue to bother people in this thread with a new issue.

[kenmcd]

.
Wadda buncha crap.

The original poster in this thread has a performance issue which cannot be blamed on the JUpgrade assets table issue.
The "it's the assets table" fix (excuse) is only going to work for some people in some situations.
For example mostly small websites which migrated using JUpgrade.
Small websites which are not likely to have the other performance issues caused by Joomla itself on larger websites.

And there are many other threads/posts about performance issues on clean installation (not upgrades).

Joomla 1.5 has performance issues on larger websites.
The solutions were found by knowledgeable users who knew enough to hack and fix the code.
Round one of head in the . . . sand.

Joomla 2.5 has worse performance issues than Joomla 1.5.
Anyone who cannot see that needs a belly button window.

The whole "don't like it fix it yourself" excuse is so offensive.
It is basically just saying "#@&k you" to anyone who dares to complain about another ridiculous mess.
<shakes head and keeps fighting the urges towards spouting many 4-letter words which will result in a forum warning>

Being the Joomla cheerleading squad and head excuse maker is not helpful to anyone here looking for real solutions.
Want to do something actually useful (and less offensive)? - help fix the queries causing the problems.


.

[garyjaybrooks]

Ken,

I should delete your forum post because it's a waste of everyone's time. I could not help but Google your name to see who you are, First few results all I see is you complaining and not showing your face. Seems the trend follows on this thread. I kindly took a screen shot of some of the negative talk I see in other areas of the internet. I could have continued with additional screen shots but I decided it is enough that I have to reply to you on this topic.

http://www.quick-markup.com/image/4f615097c7f1e << Picture painted here by you.

I'll be glad to step up to the plate. Find me a big site that is having problems performing and let's study the site. We have some of the biggest sites in the world on our servers and all is humming along very well. If this was a core Joomla! scaling issue then I would invest my personal time.

Next time you come to the forum please try to be more positive. If you have a site example that is in trouble because of core Joomla bring it to the table in a organized fashion.

Best of luck Mr. Negative.

[breto33]

So what I am hearing is this:

1. Don't complain or you will be deleted
2. Be positive or you will be deleted
3. Throw money or hours at the problem that you didnt cause
4. Stay on 1.5 which will be unsupported and unsecure in a few months.
5. Get rid of all of your content and only have a small site
6. Keep all of you site content on a large site and let it be unusable so the joomla team can study it

But be positive about your site that will soon be unsupported if you stay in Joomla 1.5 and don't complain or you will be silenced.

If this is how Joomla intends to operate, I don't have a problem with that, I just wish we would have gone a different direction when we migrated form 1.0 to 1.5. I would have rather wasted a few weeks of my time moving to another CMS if i knew I was going to have to go through the same thing when 2.5 was launched, and when the next version is launched I assume it is going to be just as painful. If this is really the strategy by joolma, go through a painful and expensive migration process every year, or stay on an unsupported and unsecure version, then what would make anyone want to stay on it?

I have been a huge cheerleader for Joomla up until now, but this has pretty much done it for me, I currently have a couple of dozen client sites running on it as well as my full time employers site, but the attitude displayed by the developers towards anyone with problems or who dares complain about problems is the final straw.

[garyjaybrooks]

Breto33,

Example case for you; If you personally install a bad part on your car and it breaks the car. oh crap! You installed and used a bad part and it hurt the main engine. What to do? You have to fix it, replace it, or start over. Its simple math. Would you expect Ford to fix your bad engine part "you" installed?. Why would you think Joomla is any different?

Your taking your comments to extreme. I volunteer for the project and I have zero to do with core code. I submit patches and bug fixes as a volunteer. You can do the same thing as me. I don't know who you talk about when you say "joomla" because as far as I know Joomla is a open source project and built on volunteers. "You" are Joomla! in this case and if you say "Joomla should fix your bad import" then you are talking about yourself. You can sit on the edge and complain or you can do what I do and try to help fix the issue. If you want to participate in helping fix the issue you can certainly join >>> signup a GITHUB account. https://github.com/joomla

Anyone would charge you a consulting fee for this labor. Nobody is telling you to pay. Invest your time if you do not have money and properly import your data to a new version of Joomla and all will work great.

Last but not least on comment 4 - I will repeat myself. People are still using Mambo to this date and I have heard zero comments about someone being hacked. You can stay on 1.5 as long as your heart desires. You do not need to move to next version.

Be positive and fix your issue If you like some help or think you have a assets table issue post a new thread and screen shot of your issue and lets try to work through it.

Gary Brooks

[jservices]

OK everyone, let us focus on the original issue here, but first...

garyjaybrooks; you are right. If we did use a third party extension to perform our upgrade and our sites now have problems then it is not the fault of the Joomla core team of developers. However, one must ask themselves why did Joomla developers not provide the proper tools for migrating all these years? They cannot in all honesty say well it is their fault when 'they' were merely trying to fill in a huge failure by Joomla developers to provide the PROPER TOOLS THEMSELVES! I mean really....this was a massive oversight by Joomla developers to neglect providing people the proper tools to migrate. What were they expecting us to do with our older sites? Trash them? Start from scratch? It seems a pretty essential function to me that when you provide a newer version of your CMS then you also provide the means to get there from previous versions, but I may be expecting too much, you all be the judge that.

Back to the issue.....

If the original problem stems from a previous migration using Jupgrade then let us look to them for some kind of solution. I just did that and I already see they do indeed acknowledge a previous bug involving the assets table. In their 2.5.0 release they mention fixing the following:

Fixing ACL issues with assets, categories and content data

Not being a programer and from my understanding of this problem the x_assets table is all about the new ACL, Access Control Lists, introduced in Joomla 1.6. As well, my understanding of the current problem with slow queries (at least in my case) has to do with a broken _assets table. I may be simplifying things here for my understanding but I think this is the general gist of it.

Now my question is if I use Jupgrade to perform the migration from 1.7 to 2.5 will it repair the damage it did earlier? I will make copies and give it a shot today. If it works then I will post it here and if it doesn't....well, I will still post it to help save you the effort. Wish me luck!

[garyjaybrooks]

You would not use JUpgrade for 1.6 to 1.7 or to 2.5. You can use core Joomla upgrade method to upgrade from 1.6 > up to 2.5 without having to deal with migration of content. The Joomla core developers kindly made sure we could upgrade without having to migrate data.

Where the issue is coming from is doing a 1.5 data migration to > 1.6,1.7,2.5 and above. Remember that 1.5 data does not slide into newest versions of Joomla without a little love. This is why people were using the Jupgrade or other migration tools.

If you have bad asset tables in 1.6, 1.7, 2.5 you either need to do the import again from your good 1.5 site or you need to manually fix your 1.6,1.7,2.5 site.

[tappy52dog]

Can anyone tell me which version is the fastest for larger sites at this time? Joomla 1.5, 1.6. 1.7, or 2.5 (in order if possible)? Is the new Joomla 2.5 version really the slowest and uses the most server resources to operate?

[cuteschweinchen]

Update after I totally redone my site with the new Joomla 2.5 - 2 weeks later my account got suspended because of causing much of the server load spike - It is having high php usage. Now my site is down

[tappy52dog]

That doesn't sound good cuteschwinchen. I guess it's better to be safe and not upgrade my 1.7 site to 2.5 then. I still don't understand why Joomla 1.7 isn't supported any longer, yet 1.5 is. Perhaps I should revert backwards to Joomla 1.5 instead of forward to 2.5?

[garyjaybrooks]

1.7 is a auto upgrade to 2.5.3, you do not have to move your data or change anything. In some cases you need to upgrade extensions and maybe template. Either way everyone should upgrade to latest Joomla using the Joomla upgrade feature.

Here is a video how to upgrade Joomla 1.7 >>> To Latest Joomla version.
http://www.[youtube].com/watch?v=-QLvw6ZDv-M

I'm closing this thread. Please open a new thread with all details to your issue if you want attention to your site issue.