Performance-Issue updating a bug

[worschtsupp]

Since a couple of weeks I notice a performance issue using mantis: everything works fine but updating a bug (only updating!) -e.g. adding a note or a related bug- takes at least 5 or 6, sometimes up to 10 seconds!

I'm using Mantis 1.2.0, git-Version, updating sometimes. I'd been starting with 1.1.8, changed to 1.2.RC2 an d now -a said, using the GIT / nighly-build-
When I do a clean / fresh setup with an empty (MySQL)-DB, no problems.
The problems are not the DB-Calls and the DB is very small, it must be some project-specific settings. But which?

Has anyone any idea or hint?
Is there a way to export the data from the existing database and to import them in a "clean" database? This way I could verify that the problem is not db-related.

System is: winXP, php 5.2.12, MySql 5.1.x, Apache 2.2

[worschtsupp]

*bump*...

Nobody in outer-space who encounters similar problems?

[atrol]

to get more details about database activity set temporarely option show_queries_list to value 1

[worschtsupp]

Thanks atrol, I know this option and tried it already. I cound't see something wrong, although I'm not the query-specialist. As I said, don't think the database to be the problem. Just wondering which component is consuming the time and how to figure out that.

Any other idea left?

[atrol]

As I said, don't think the database to be the problem.

Sure?

...This way I could verify that the problem is not db-related.

some more things maybe worth examining:
- did you optimize all tables of your database? (easiest way with phpMyAdmin or MySQL administrator)
- is your CPU busy with one of the processes during the operation?
- diff your config_inc.php with a fresh config_inc.php of a new installation
- have a look at Manage -> Manage Configuration -> Configuration Report , is there anythin more than entry database_version?

[worschtsupp]

First of all: thanks for the tips.

- did you optimize all tables of your database? (easiest way with phpMyAdmin or MySQL administrator)

Yes, I did, but no change. And by the way: it's really a small DB with 4 projects, each with not more than 20-30 issues.

- is your CPU busy with one of the processes during the operation?

No. Not at all. All CPUs say "how boring, waiting for work

- diff your config_inc.php with a fresh config_inc.php of a new installation

Sure I can do this. But I will only find the changes that I made intentional. And they worked before whatever happened. I removed all of them and removed them one by one: no success.

- have a look at Manage -> Manage Configuration -> Configuration Report , is there anything more than entry database_version?

Yes, there are. Changes concerning
excel_columns / csv_columns for all_projects
set_status_threshold
status_enum_workflow
view_issues_page_columns

plugin_XmlImportExport_schema -1
plugin_MantisGraph_schema -1
plugin_MantisCoreFormatting_schema -1

Not sure if there is something wrong.

If their is a way to export the data of a project (if I loose the history it's ok) and to import them in a fresh and good install it would be ok. Do you know such a way? I found and "import" function somewhere in mantis, but no description what the format of the import has to be and how to export data.

[atrol]

I see that you installed the plugin "Import/Export issues 1.0"
I never tried myself, but this should do the work.
For every project do the following:
Go to "View Issues" page and choose "XML Export"
In your new installation create the same projects and categories, then choose "Manage" -> "Import Issues"

Just another speculation
Uninstall "Mantis Graphs" and the "Import/Export issues" plugin and check whether the performance changes

[worschtsupp]

Thanks for these hint's. I'll try them when some time is left and let you know the result.

[atrol]

If you try a further fresh install start with 1.2.0RC2 to figure out whether behaviour is caused by the changes in the nightly builds.
I have one test installation on a slow host with a nightly build from Dec. 29th where updating a bug (3-4 seconds) takes longer than creating a new one (2 seconds)
I have another test installation with a pure 1.2.0RC2 where updating a bug works fast. But this is not comparable, because it's hosted on another computer.
I hope there will be soom a RC3 or a 1.2.0 final, because searching for bugs and performance issues in nightly builds is sometimes a waste of time.