@franzpeter try to empty your trash for items, menus, categories and try again

There is no trash inside items, menus and categories. I did test it with different installations. I think it has something to do with the way the progress bar operates (output buffering or so).

@franzpeter how much content do you have on your site?
you have this problem on the clear Joomla installation?
or you got this problem after install some additional component/plugin?
and can you please check the browser console, is there any error while indexing?

I did a clean install, so nothing except of the default example data: learn Joomla. I see the same: it takes a while until receiving a progress indication. It is somehow staggered not fluent. Maybe it should be that way. I do not know.

I did try it with an old J 2.5 installatiion too, there is a direct progress indication, while with J 3 it takes a while if there is more content to index until receiving the first response for progress bar. It seems to have something to do with buffering but the question is: Why on the same localhost with the same configuration J 2.5 delivers direct response while with J 3 it takes a while to show something. If there is not very much content, it will not show the indexing process and the first response occurs while optimizing tables. If there is more content to index, it takes a while for first response (the green progress bar for indexing).

It can take a while for it to respond with the first notice, but it is true that it also may stall underway.
Have you tried lowering the numbers in the settings?

For the stalling, I'd propose to just alert the error out so the user isn't sitting for hours thinking it is just slow?

@franzpeter I’ll just say that #5433 and #5386 were the two PR’s responsible for all the bootstrap changes. You can trace the changes yourself and see that there were no changes in the PHP part responsible for the the data provided for the ajax part. Also the javascript itself responsible for the updating of the messages and the progress bar is just touched only to change the mootools part to Jquery.
But I have to mention that one of testers had a similar problem with very slow performance and we finally traced it down to some trashed content, which once deleted performance was restored. I guess the indexer php code needs some improvements here and there but I am quite busy right now to dig into that, if you can make some improvements I surely will provide some tests and feed back.

A little idea: when I click on index button, maybe, a little bottom bar appear with a realtime feedback.

Hi @franzpeter You created this issue sometime ago but have not provided any code for people to evaluate. As no one else has done so either and there is no clearly defined way to reproduce the problem, I am closing this issue at this time. If code is provided (a pull request) it can always be re-examined.

Set to "closed" on behalf of @chrisdavenport by The JTracker Application at issues.joomla.org/joomla-cms/6812