Re: [rt-users] [repost] Performance-Bug in SelfService when updated from 3.6.1 to 3.6.3

Hello, does anybody have the same performance degration on 3.6.3 SelfService/index.html or do I have to dig into our special configuration?? If the latter, does anybody have a hint where to dig into? Dirk. --Am 23. Januar 2007 08:39:38 +0100 schrieb Dirk Pape [EMAIL PROTECTED]: Hello,

Re: [rt-users] [repost] Performance-Bug in SelfService when updated from 3.6.1 to 3.6.3

I On Sat, Jan 27, 2007 at 09:29:17AM +0100, Dirk Pape wrote: Hello, does anybody have the same performance degration on 3.6.3 SelfService/index.html or do I have to dig into our special configuration?? If the latter, does anybody have a hint where to dig into? I haven't seen it. It

[rt-users] RE: Asset Tracker with RT 3.6

Hi, i've upgraded RT from 3.4.5 (AT installed) to RT 3.6.3, no Problems, runs fine! Torsten -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Philip Kime Sent: Friday, January 26, 2007 6:44 PM To: rt-users@lists.bestpractical.com Subject: RE:

Re: [rt-users] Trying to develop a query

Philip J. Hollenback escreveu: [...] So is there a way to narrow this query to only tickets not updated by their owner in the last week? Ideally I guess there would be a variable LastUpdatedByOwner instead of just LastUpdated. There is a LastUpdatedBy search field, that could help you,

Re: [rt-users] (ERRATA) Mysql to Postgres Problems

[..] I considered migrating a couple weeks ago. I wrote a tutorial[1] about [...] 1 - http://www.safernet.org.br/twiki/bin/view/Colaborar/RT_MySQL2Pg -- Gilmar Santos Jr ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community

Re: [rt-users] Mysql to Postgres Problems

Hello Mario, I considered migrating a couple weeks ago. I wrote a tutorial[1] about it and a Perl script to help with the process. I've just added a few instructions at RT wiki. We have almost 400.000 tickets and had serious performance problems. Pg performed much worse than MySQL, even after

Re: [rt-users] [repost] Performance-Bug in SelfService when updated from 3.6.1 to 3.6.3

Hi Jesse, --Am 27. Januar 2007 03:36:24 -0500 schrieb Jesse Vincent [EMAIL PROTECTED]: I haven't seen it. It _does_ look like htat query is qgetting built wrong. I wonder if changing the search to be Watcher = rather than what it is now would make it all better. you are right. Switching

Re: [rt-users] [repost] Performance-Bug in SelfService when updated from 3.6.1 to 3.6.3

On 1/28/07, Dirk Pape [EMAIL PROTECTED] wrote: Hi Jesse, --Am 27. Januar 2007 03:36:24 -0500 schrieb Jesse Vincent [EMAIL PROTECTED]: I haven't seen it. It _does_ look like htat query is qgetting built wrong. I wonder if changing the search to be Watcher = rather than what it is now would

Re: [rt-users] [repost] Performance-Bug in SelfService when updated from 3.6.1 to 3.6.3

Hello, --Am 27. Januar 2007 22:18:04 +0100 schrieb Dirk Pape [EMAIL PROTECTED]: you are right. Switching to Watcher instead of ( Requestor, Cc, AdminCc ) helps. thanks Jesse for help and Ruslan for explaination. Here is the simple patch. Dirk. performance_of_selfservice.patch

[rt-users] patch for 3.6: correcting display logic in navigation menu after a search has been performed

Hello, in RT 3.6 after a search has been performed the Ticket/Element/Tabs added submenus to two different menu items ('Show Results' and 'Tickets'). In the new 3.5 style css this had the strange effect that the navigation submenu (' First | Prev | Next | Last ') moves to the page menu

Re: [rt-users] [repost] Performance-Bug in SelfService when updated from 3.6.1 to 3.6.3

Dirk Pape escreveu: [...] If the latter, does anybody have a hint where to dig into? Try to increase innodb_buffer_pool_size in my.cnf. See [1], [2] and [3]. Tunning some parameters like join_buffer_size, innodb_buffer_pool_size and some others gave me a huge performance improvement. Take care