Reports takes minutes to compleet

[omry at yadan dot net]

My database contains about 35 tickets. recently reports started to work very slowly. when I open a report, apache cpu usage spikes to 100% for a few minutes (!) and then I get the results. I inserted the sql query directly into sqlite3, and it returned instantly

---

Note: this is a problem with the wiki engine, when rendering attachment:ticket35.txt​
— cboos

[omry]

if you need my database or anything else to reproduce, just ask.

[Christian Boos]

Can you first try if this is reproductible for you using tracd?

[omry]

it is.

[omry]

I mean, it is reproduceable with tracd.

[omry]

my database file. (sqlite 3)

[omry]

assigned to milestone 0.10.1

[Emmanuel Blot]

Do not assign a milestone without providing a reason or a patch.

Please describe your environment (version of the OS, Python, Svn, Pysqlite, etc.)

[omry]

Debian etch. Kernel 2.6.15. Python 2.4 SVN 1.3.2 pysqlite: 1.1.7-2 AND 2.3.2-1 (could this be the problem?)

[anonymous]

and sqlite 3.3.7

[trac@…]

registered email.

[trac@…]

figured it out: ticket 35 in the attached database had a long message insife ![brackets]. when I deleted it from the database all went back to normal.

[Christian Boos]

hm, that's not a good reason to take minutes… Can you please copy/paste that message in a block, here? (or attach it?)

[trac@…]

I removed it from my database, but its in the attached file. ticket 35.

[franck34]

After upgrade sqlite2 → sqlite3, got same problem. Very slow and httpd > 99% CPU (eaccelerator website …)

[franck34]

sorry, i forgot some things: Fedora Core 3, Python 2.4 Trac 0.9.3

Before update sqlite, everything was ok.

[anonymous]

franck34, as an emergency care, find the bad ticket and remove it from the database. you can do it by viewing all the tickets on at a time till you find the slow one. there was no obvious way to remove the ticket, but I found something after some searching.

[franck34]

Very good !

I found a ticket with a description > 300 000 chars.

I've change the description of this ticket and i put 99% of the description in an attachement instead of directly in the description.

Now everything is ok, problem solved for me.

[franck34]

As suggested by matt_good on irc, request feature as been written in ticket #3944

[anonymous]

My problem is not due to a huge ticket size. I extracted the ticket content from the database and I am attacing.

[Christian Boos]

Right, problem reproduced. Thanks for having extracted the ticket35.txt ;)