It takes about 10-11 seconds to move from one page to the next. Is this typical or something wrong with my setup?
I'm using ABE 1.2 and my
I'm using ABE 1.2 and my scientific time is using the windows clock on watching the seconds hand. I have timed most of the pages laoding in the 10 second area. I would like users to be able to use the portal but I feel it is too slow to introduce that funtionality to them at this point.
would you prefer the
would you prefer the interface to take priority at the expense of call quality? Using mysql instead of csv for call records would yield faster results. The user portal primarily does lookups from the astdb. I would seriously consider using a 1.4 version of ABE its AMI is much improved over the 1.2 version.
Slow with Apache
I replaced miniserv.pl with apache but it was still just as slow. This is something we just have to live with? 10 seconds to load a web page is a long time.
manager login/out
One of the slowest pages is the call forward page in the user portal. When i click on that page i see that the manager interface was logged into 77 times. It seems like thirdlane is logging in and out for each command executed. A potential optimization is to log in and out once and execute all the commands in one manager session. Luckily asterisk fixed the memory leak bug relating to managers logging in and out a couple years ago!
Is this an issue that is
Is this an issue that is being worked on? Is there a thirdlane roadmap and if so is this on there? This is an indication to me that customers are not using the web interface extensively, if they were they would be making a lot more noise about this issue.
did you upgrade to the latest
did you upgrade to the latest version?
2010-01-25 Changed code for getting tenant settings from astdb - now it is done in one request.
2010-01-25 Changed code for getting user settings from astdb - now it is done in one request.
Clarification
My test that captured 77 manager login/logouts was not running on the latest version, it was .78. Reran test on .79 and it still took 5 seconds to load the call forward user portal page but there was an improvement. Wireshark shows the following:
t=0 seconds to t=~3 seconds the only network activity i see is between port 10000 (webmin) and the browser.
t=~ 3 seconds to t =~ 4 seconds we have 4 manager logins/logouts. Here were the commands run on the manager interface:
Action: Challenge..AuthType: MD5....
Action: Login..AuthType: MD5..Key:
Action: Logoff....
Action: Challenge..AuthType: MD5....
Action: Login..AuthType: MD5..Key:
Action: Logoff....
Action: Challenge..AuthType: MD5....
Action: Login..AuthType: MD5..Key:
Action: Command..Command: database show TL/6001....
Action: Logoff....
Action: Challenge..AuthType: MD5....
Action: Login..AuthType: MD5..Key:
Action: Command..Command: module show....
Action: Logoff....
my browser ultimately gets the screen at around t = 5 seconds.
I tested every other link in the user portal and they all take 5 seconds to load.
I tested several other links under webmin for different modules and they loaded in under 1 second.
I watched my system utilization and each time i click a link in the thirdlane user portal it pegs my cpu at 100% for about 2 seconds.
Processor Info for these tests:
model name : Intel(R) Pentium(R) M processor 1.86GHz
More Testing
I retested on a different processor (in order to avoid the ridicule of submitting test results from a laptop ;) )
Test Results on TL Version .78:
Averaged 13 seconds opening the call forwarding page.
Test Results on TL Version .79:
Averaged under 3 seconds opening the call forwarding page.
Processor Info for these tests:
model name: Intel(R) Xeon(R) CPU E5420 @ 2.5 GHZ
This is a Quad Core Processor and I've got two of them in the system.
This is a huge improvement from .78 to .79! Excited about the optimizations you have in the pipeline! Thanks!
some new suggestions about
some new suggestions about turning pbxmanager into a CRM is likely to create slow downs in the UI again. It seems some people arent content actually running a real CRM to keep their customer details but rather have every page pulling up reference material about their customers instead of limiting the UI to information specifically related to the phone system itself.
If you feel as I do, that the UI should stay as lean as possible so that the number of tenants you can get on a box remains close to 1000 instead of a couple hundred, make sure to speak in defense of a lean UI at:
Ive never timed it but, depending on the page, it has to do a lot of things like determine if its asterisk 1.2, 1.4, 1.6 or CallWeaver, and bypass the code for the remaining possibilities. Some pages take longer than others and the length grows as more users are added to the system.