Hello List,
Hello Jesse!
I finally managed to get my apache-1.3 and fastcgi to run rt3. I
imported data from our rt2 instance as well (custom templates/scrips
using custom templates were ignored).
RT3 seems to run, but very(!) slowly on a 1Ghz P4 with 1Gig of RAM. Is
decent performance to be expected from such a setup (about 250 users/8
admins/2500 Tickets per year)? First impression is fine, though.
When trying to access a queue via Quick search, I get the following
error:
System error
error: Can’t locate object method “CountAll” via package "RT::Tickets"
at /opt/rt3/lib/RT/Tickets_Overlay.pm line 1698.
context:
…
277: }
278:
279: # All errors returned from this routine will be in exception form.
280: local $SIG{‘DIE’} = sub {
281: rethrow_exception( $_[0] );
282: };
283:
284: #
285: # $m is a dynamically scoped global containing this
…
code stack: /usr/lib/perl5/site_perl/5.8.0/HTML/Mason/Request.pm:281
/opt/rt3/lib/RT/Tickets_Overlay.pm:1698
/opt/rt3/share/html/Search/Listing.html:105
/opt/rt3/share/html/autohandler:146
any hints?
Regards
Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg
And another addition: When trying to access the ‘Jumbo’ view of a
ticket, MySQL uses up all of the CPU time, and after a timeout I get an
internal server error from the server. Restarting MySQL gets the system
up again
(RH8.0,Apache1.3.27,fastscgi,perl5.8.0,mysql-4.0.4).
Regards,
Harald
Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg
similiar issue i’ve right now with follow constellation:
freebsd 4.6/mysql3.23.55/apache1.3.27/modperl1/rt-2-1-88
if i open a ticket and try to add for example a comment, the
mysql-process goes up to over 85%CPU-Load and i get an timeout 
cheers,
geri
-----Ursprungliche Nachricht-----Von: rt-devel-admin@lists.fsck.com
[mailto:rt-devel-admin@lists.fsck.com]Im Auftrag von Harald Wagener
Gesendet: Freitag, 14. Marz 2003 14:24
An: rt-devel@lists.fsck.com
Betreff: Re: [rt-devel] rt-2-1-88: real progress
And another addition: When trying to access the ‘Jumbo’ view of a
ticket, MySQL uses up all of the CPU time, and after a timeout I get an
internal server error from the server. Restarting MySQL gets the system
up again
(RH8.0,Apache1.3.27,fastscgi,perl5.8.0,mysql-4.0.4).
Regards,
Harald
Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
similiar issue i’ve right now with follow constellation:
freebsd 4.6/mysql3.23.55/apache1.3.27/modperl1/rt-2-1-88
if i open a ticket and try to add for example a comment, the
mysql-process goes up to over 85%CPU-Load and i get an timeout
Just for the record: I have the same problem with commenting on tickets
as well…
Regards,
Harald
(RH8.0/apache 1.3.27/fastcgi2.0.40/perl-5.8.0/MySQL-4.0.4)
Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg
This is probably due to DBIx::SearchBuilder being only version 0.79.
0.80 is only available via CPAN, did not see it in the devel/ directory
of bestpractical’s download area.
This certainly resolved my QuickSearch problem. The MySQL problems
persist…
Regards,
Harald Wagener
Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg
Just for the record: I have the same problem with commenting on tickets
as well…
Hi!
Did you use InnoDB tables? I don’t have the posting at hand, but I saw an
email from Jesse (today or yesterday) stating that you MUST use InnoDB
tables, since MyISAM causes a HUGE performance impact.
Regards,
Martin
Just for the record: I have the same problem with commenting on
tickets
as well…
Hi!
Did you use InnoDB tables? I don’t have the posting at hand, but I saw
an
email from Jesse (today or yesterday) stating that you MUST use
InnoDB
tables, since MyISAM causes a HUGE performance impact.
I think so. How do I find out after the fact? I do have some ib*
files in /var/lib/mysql; in /var/lib/mysql/rt3, there are *.frm files
for all the tables in RT, except for sessions, which seems to be MyISAM
files (sessions.MYD, sessions.MYI).
Regards,
Harald
Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg
I think so. How do I find out after the fact? I do have some ib*
files in /var/lib/mysql; in /var/lib/mysql/rt3, there are *.frm files
for all the tables in RT, except for sessions, which seems to be MyISAM
files (sessions.MYD, sessions.MYI).
show table status\G.
Should have show “Type: InnoDB” for each table. Otherwise you can do an
‘alter table
type=Innodb;’
It occurs to me that it hasn’t recently been stressed enough that MySQL
itself must be configured to take advantage of system memory. Out of
the box, it comes configured to use something like 64mb of RAM. The more
ram you let mysql have, the faster it will be. It’s also worth moving up
to a more recent mysql (4.0.9+) and enabling mysql’s built in “Query
Cache” which is known to give a huge performance boost for certain types
of applications.
JesseOn Fri, Mar 14, 2003 at 02:23:55PM +0100, Harald Wagener wrote:
And another addition: When trying to access the ‘Jumbo’ view of a
ticket, MySQL uses up all of the CPU time, and after a timeout I get an
internal server error from the server. Restarting MySQL gets the system
up again
(RH8.0,Apache1.3.27,fastscgi,perl5.8.0,mysql-4.0.4).
Regards,
Harald
–
Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
Jesse,
Have you got any tips (or pointers to pages) for that? We use
MySQL for bugzilla and bonsai as well, and it could definitely use a
performance boost. We’ve got it on some fairly serious (IBM server dual
cpu’s, raid 5, etc) hardware, and it’s still the weak link…
Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677
kfh@mqsoftware.comFrom: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Friday, March 14, 2003 1:02 PM
To: Harald Wagener
Cc: rt-devel@lists.fsck.com
Subject: [rt-devel] MySQL Performance issues with RT 2-1-xx
It occurs to me that it hasn’t recently been stressed enough that MySQL
itself must be configured to take advantage of system memory. Out of
the box, it comes configured to use something like 64mb of RAM. The more
ram you let mysql have, the faster it will be. It’s also worth moving up
to a more recent mysql (4.0.9+) and enabling mysql’s built in “Query
Cache” which is known to give a huge performance boost for certain types
of applications.
Jesse
And another addition: When trying to access the ‘Jumbo’ view of a
ticket, MySQL uses up all of the CPU time, and after a timeout I get
an
internal server error from the server. Restarting MySQL gets the
system
up again
(RH8.0,Apache1.3.27,fastscgi,perl5.8.0,mysql-4.0.4).
Regards,
Harald
–
Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Jesse,
Have you got any tips (or pointers to pages) for that? We use
MySQL for bugzilla and bonsai as well, and it could definitely use a
performance boost. We’ve got it on some fairly serious (IBM server dual
cpu’s, raid 5, etc) hardware, and it’s still the weak link…
Best starting point is
http://www.mysql.com/doc/en/MySQL_Optimisation.html
Cheers,
-Rich
Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | Save The Pacific Northwest Tree Octopus
rich@lafferty.ca -----------±----------------------------------------------