On 01/09/2013 05:08 AM, Tim Gustafson wrote:
http://bestpractical.com/rt/docs/latest/RT_Config.html#FullTextSearch
http://bestpractical.com/rt/docs/latest/full_text_indexing.html
These are also shipped with RT itself as doc in etc/RT_Config.pm and
docs/full_text_indexing.pod.
Hrmm, I remember
in the
bug, I simply don't have time to cover all the angles required for a
full upstream fix.
Cheers, Jeff.
--
Jeff Fearn jfe...@redhat.com
Senior Software Engineer
Red Hat
On 04/13/2012 11:32 AM, Kenneth Crocker wrote:
Florin,
create a search that meets your criteria and then a dashboard that runs
said search at the appropriate time.
Kenn
On Wed, Apr 11, 2012 at 2:33 PM, Florin Andreiflo...@andrei.myip.orgwrote:
Using RT-4.0.5 on Linux.
What is the best way
Hi, using RT 4.0.2 and DBIx::SearchBuilder 1.61 (also tested 1.59) I can
reliably create a search using the RT4 GUI that locks up the database.
It appears that the search used to generate the 'Found X tickets' text
generates a large set of joins which murders MySQL :(
The query is a simple
On 07/27/2011 06:38 PM, john s. wrote:
Hello Jeffry
Due to your really large RT Environment...
I have tested
rt 4.0.0.1
and rt 3.8.9
only with a few user and tickets ..
maybe rt 4 can handle large rt instances much better than rt 3.8.8 and by
the othe one is vice versa?
so if this isn't
On 07/26/2011 11:32 PM, Kevin Falcone wrote:
On Tue, Jul 26, 2011 at 10:29:19AM +1000, Jeff Fearn wrote:
On 07/26/2011 02:34 AM, Adam Thompson wrote:
Set($AutocompleteOwners, 1);
Compare the display time Tickets-New Search
With AutocompleteOwners: Time to display: 0.442697
Without
On 07/26/2011 02:34 AM, Adam Thompson wrote:
I can't speak for the dev team, but I have noticed a distinct trend:
Apache+mod_perl is very slow with RT4.0.
Lighttpd+FCGI is fast with RT4.0.
Standalone PSGI is really fast with RT4.0 (but not very scalable unless
you know what you're doing).
I
On Mon, 2011-02-14 at 13:39 -0600, Max McGrath wrote:
Hello -
We are using RT 3.8.8 on Ubuntu 10.04.
We are looking for a simple way to track how our tickets are being
created. Right now tickets get created in any number of way:
* User e-mails problem directly to RT
*
On Thu, 2010-09-09 at 22:52 -0400, Jesse Vincent wrote:
On Thu, Sep 09, 2010 at 08:15:37AM +0100, Justin Hayes wrote:
We gave those patches a try. Shaved ~4s from our 20s, which isn't bad so we
might look at rolling them into Live.
Justin,
Have you tried running ticket loads under
On Fri, 2010-07-09 at 12:45 -0700, Kevin Gagel wrote:
Enter into Perl:
perl -MCPAN -e shell
Have perl recomend updateds:
r
Update the XML::RSS and XML::Parser modules and any others that RT is
using.
Sorry for the delay in replying to this, I have been on medical leave.
IMHO you are
this because it is based on some code I found somewhere
on the web and for the life of me I can no longer find the source to
reference :(
Cheers, Jeff.
--
Jeff Fearn jfe...@redhat.com
Software Engineer
Engineering Operations
Red Hat, Inc
___
http
11 matches
Mail list logo
