We use RT 3.8.1 (gentoo,apache2,mod perl) for use with our sales team
for Safaris in Tanzania. We have extremely poor internet connectivity
from Tanzania (no fibre yet) - our ISP has less transit B/W than most of
you have to your homes! and 800ms latency. It is therefore important to
us to keep b/w usage to a minimum. If you’ve every used a 14.4modem, its
like that!
I have a few ideas to help this and have searched the net without luck.
I can code basic perl.
I’d like to automatically strip sigs from emails stored in the
database, so the Ticket’s page is not so long with all the transactions
can anyone suggest where i should put the code to do:
I’d like to parse the transaction through something like uniq(1) to
get rid of duplicate lines, and also to remove lines that are:
to only one line.
where should i put this code? in a scrip, or in local/lib/RT? which
module? I think i can write the code, but need advice on the correct way
to go about it.
I’d like to only display the last few emails for a ticket, and even
then, maybe only the first 5-6kb of a email - our clients reply without
trimming mails to relevant detail, and threads can be over 50 mails
long! that can make a display ticket page over a MB in some cases. I
thin this may be a larger hack.
If anyone else has any great ideas about how to optimise RT for low
bandwidth, I’d love to know!
thanks in advance
Woody.
Richard Wood (Woody)
Managing Director
Wild Thing Safaris Ltd.
PO BOX 34514 DSM
Office: +255 (0) 222 617 166
Mobile: +255 (0) 773 503 502
Hi Richard,
not done this till now, but i think if you strip up the css this will offer
you a better performance. But not sure if someone else did this already.
We use RT 3.8.1 (gentoo,apache2,mod perl) for use with our sales team
for Safaris in Tanzania. We have extremely poor internet connectivity
from Tanzania (no fibre yet) - our ISP has less transit B/W than most of
you have to your homes! and 800ms latency. It is therefore important to
us to keep b/w usage to a minimum. If you’ve every used a 14.4modem, its
like that!
I have a few ideas to help this and have searched the net without luck.
I can code basic perl.
I’d like to automatically strip sigs from emails stored in the
database, so the Ticket’s page is not so long with all the transactions
can anyone suggest where i should put the code to do:
I’d like to parse the transaction through something like uniq(1) to
get rid of duplicate lines, and also to remove lines that are:
to only one line.
where should i put this code? in a scrip, or in local/lib/RT? which
module? I think i can write the code, but need advice on the correct way
to go about it.
I’d like to only display the last few emails for a ticket, and even
then, maybe only the first 5-6kb of a email - our clients reply without
trimming mails to relevant detail, and threads can be over 50 mails
long! that can make a display ticket page over a MB in some cases. I
thin this may be a larger hack.
If anyone else has any great ideas about how to optimise RT for low
bandwidth, I’d love to know!
thanks in advance
Woody.
Richard Wood (Woody)
Managing Director
Wild Thing Safaris Ltd.
PO BOX 34514 DSM
Office: +255 (0) 222 617 166
Mobile: +255 (0) 773 503 502
Hi Richard,
not done this till now, but i think if you strip up the css this will offer
you a better performance. But not sure if someone else did this already.
RT already concatenate css in to one css file with CSS::Squish. It
doesn’t “compact” them thought.
Quote from CSS::Squish README:
It is possible that feature versions will include methods to compact
whitespace and other parts of the CSS itself, but this functionality is
not supported at the current time.
We use RT 3.8.1 (gentoo,apache2,mod perl) for use with our sales team
for Safaris in Tanzania. We have extremely poor internet connectivity
from Tanzania (no fibre yet) - our ISP has less transit B/W than most of
you have to your homes! and 800ms latency. It is therefore important to
us to keep b/w usage to a minimum. If you’ve every used a 14.4modem, its
like that!
I have a few ideas to help this and have searched the net without luck.
I can code basic perl.
First up, you probably want to use mod_gzip. That will be a HUGE
improvement for your users and will get a lot more improvement than
little content hacks like you’ve been pondering.
Jesse
First up, you probably want to use mod_gzip. That will be a HUGE
improvement for your users and will get a lot more improvement than
little content hacks like you’ve been pondering.
Jesse
Hi Jesse et al,
That was an excellent suggestion, tho after some digging mod_gzip is
apache1 and its mod_deflate in apache2. I’ve implemented it and it was
trivial on gentoo - i added to httpd.conf
my pages are now 25% of the total size, and the text content < 20% - a
huge saving - so i don’t really need to reduce the number of tickets
displayed any more. cool.
I’d still like to strip the sigs and > > > tho - they annoy me!
scrip, or in the perl? any hints…
thanks for your help. It will really make a difference to our workforce.
Woody.
Richard Wood (Woody)
Managing Director
Wild Thing Safaris Ltd.
PO BOX 34514 DSM
Office: +255 (0) 222 617 166
Mobile: +255 (0) 773 503 502
First up, you probably want to use mod_gzip. That will be a HUGE
improvement for your users and will get a lot more improvement than
little content hacks like you’ve been pondering.
Jesse
Hi Jesse et al,
That was an excellent suggestion, tho after some digging mod_gzip is
apache1 and its mod_deflate in apache2. I’ve implemented it and it was
trivial on gentoo - i added to httpd.conf
my pages are now 25% of the total size, and the text content < 20% - a
huge saving - so i don’t really need to reduce the number of tickets
displayed any more. cool.
I’d still like to strip the sigs and > > > tho - they annoy me!
scrip, or in the perl? any hints…
search for Text::Quoted in the code
thanks for your help. It will really make a difference to our workforce.
Woody.
–
Richard Wood (Woody)
Managing Director
Wild Thing Safaris Ltd.
PO BOX 34514 DSM
Office: +255 (0) 222 617 166
Mobile: +255 (0) 773 503 502