Hi there;
Has anyone any experience/thoughts/suggestions on what version of dbix is
best suited for rt-3.4.4.
We upgraded to 3-4.4, at the same time we’v upgraded dbix to version
1.33, a
month down the line fighting the degradation in performance and persistant
bugs, I am starting to wonder if the dbix upgrade was premature and should
roll back to version 1.27 ??
Any suggestions??
my system is mod_perl 2.0 /apache 2 / mysql 4.1.14…
symtoms: searches are much slower than were on version 3.2.3
display long Tickets (200+) updates much slower and sometimes browser gives
up
Query builder (saved search bugs)
Case:
I am been trying to deal with Attribute::Name bug within query builder,
investigating rt-3.5.5 for possible fixes came accross this in
SearchBuilder.pm:
use DBIx::SearchBuilder “1.27”;
Roy
Hi there;
Has anyone any experience/thoughts/suggestions on what version of dbix is
best suited for rt-3.4.4.
We upgraded to 3-4.4, at the same time we’v upgraded dbix to version
1.33, a
month down the line fighting the degradation in performance and persistant
bugs, I am starting to wonder if the dbix upgrade was premature and should
roll back to version 1.27 ??
Any suggestions??
my system is mod_perl 2.0 /apache 2 / mysql 4.1.14…
symtoms: searches are much slower than were on version 3.2.3
display long Tickets (200+) updates much slower and sometimes browser gives
up
Can you tell us what performance tuning you’ve done?
Query builder (saved search bugs)
See ruslan’s proposed patch.
Case:
I am been trying to deal with Attribute::Name bug within query builder,
investigating rt-3.5.5 for possible fixes came accross this in
SearchBuilder.pm:
use DBIx::SearchBuilder “1.27”;
That just says “and if you use something before 1.27, scream bloody
murder.”
Hi;
Jesse Vincent wrote:
Can you tell us what performance tuning you’ve done?
Can you please advise on what I should/should n’t have done.
indexes:
Index on Principals(Disabled)
index Group3 on Groups(Instance);
index Group4 on Groups(Type);
schedule optimise tables
re applied rights --more global-- then deleted old rights shrinking the
acl table …(this unexpectedly made a big difference).
Used shredder to remove unwanted users …
Modified UserHasRight to skip (query tables to previlidge check ) for
certain members on certain rights.
modified build.html changed Owner list from drop down to free text (this
made a big difference), my owners list is about 600 users
Contemplating applying your patch submitted to users list (clone/rights
patch)
Query builder (saved search bugs)
See ruslan’s proposed patch.
I must have missed this though I am keeping eagle eye to any solution to
this issue, can you tell me where I can find this patch, its not on the
wiki nor in my saved lists emails (All of them as far as I know)
That just says “and if you use something before 1.27, scream bloody
murder.”
Ahh ok, i guess it depends on which moment in time you read that.
Many thanks;
Roy
Hi;
Jesse Vincent wrote:
Can you tell us what performance tuning you’ve done?
Can you please advise on what I should/should n’t have done.
First off, I’d look at they mysql server config file to make sure you’ve
told it to use more than 64MB of RAM. There are a number of mysql tuning
guides out there. We also offer configuration assistance as a commercial
service if you’re out of your depth.
See ruslan’s proposed patch.
I must have missed this though I am keeping eagle eye to any solution to
this issue, can you tell me where I can find this patch, its not on the
wiki nor in my saved lists emails (All of them as far as I know)
He sent it out sometime in the last 18 hours. Your name was in the first
line of the message, iirc.
Jesse Vincent wrote:
First off, I’d look at they mysql server config file to make sure you’ve
told it to use more than 64MB of RAM. There are a number of mysql tuning
guides out there. We also offer configuration assistance as a commercial
service if you’re out of your depth.
I just stated what I did since upgrade from 3.2.3 to 3.4.4, As far as I
and the team know (we also offer similar services to our clients) mysql
is optimised , I am sure your experience will be most valuable and trust
me I am trying since your earlier mail to me few weeks back regarding
paying customers (I bought the book does that help ).
in any case:
max_allowed_packet = 8M
net_buffer_length = 128K
max_connections = 150
key_buffer = 2048M
myisam_sort_buffer_size = 512M
join_buffer = 16M
read_buffer = 16M
sort_buffer = 16M
read_rnd_buffer = 16M
table_cache = 2048
thread_stack = 1M
thread_cache = 128
wait_timeout = 1800
connect_timeout = 60
max_connect_errors = 10
query_cache_limit = 32M
query_cache_size = 768M
query_cache_type = 1
#thread_concurrency = 1
tmp_table_size = 384M
The system has 6G mem and used for Mysql only, the web server run of
different hardware.
BTW: there is a long history behind the myisam … innodb is not much
different (for us any way) we have 2 dev environments one of each, and
performance differences is negligible.
The above config was the same with version 3.2.3 which was running very
smoothly, my main issue is that 3.4.4 is not as efficient why and what
can we do to make it run as 3.2.3 was running.
See ruslan’s proposed patch.
I must have missed this though I am keeping eagle eye to any solution to
this issue, can you tell me where I can find this patch, its not on the
wiki nor in my saved lists emails (All of them as far as I know)
He sent it out sometime in the last 18 hours. Your name was in the first
line of the message, iirc.
Apologies …mail filters and gmail.
Thanks Ruslan.
Roy
When I upgrade DBIx::SearchBuilder, and then do the ‘r’ command to see what
other Perl modules need updating, DBIx::SearchBuilder::Report shows up. Ok,
fine.
When I install/upgrade that, though, it seems to revert DBIx::SearchBuilder,
as a subsequent ‘r’ command shows DBIx::SearchBuilder as being v1.01 and
"needing" v1.10 again.
I’m not enough of a Perl guru to know what to fix/patch/etc. Anyone have any
ideas??
TIA.
When I upgrade DBIx::SearchBuilder, and then do the ‘r’ command to see what
other Perl modules need updating, DBIx::SearchBuilder::Report shows up.
Whoops. I actually meant DBIx::SearchBuilder::Record –
cpan> r
Package namespace installed latest in CPAN file
DBIx::SearchBuilder::Record undef v36.86.69.82.83.
J/JE/JESSE/DBIx-SearchBuilder-1.01.tar.gz
2 installed modules have a version number of 0
210 installed modules have no parseable version number