tycho
Guru (not...)
- Joined
- Aug 9, 2011
- Messages
- 652
- Reaction score
- 272
I finally got around to tweaking my old Dockstar so that it handles the I-PBX image (see http://nerdvittles.com/?p=10560) more gracefully. (fn1) I very much like my cheapie Pogo Mobile -- best $10 PBX I ever had -- and find that it is uber reliable and essentially bullet-proof. But, it has a processor clock speed of 800MHz, whereas my much-older Dockstar using the same architecture has a clock speed of 1.2GHz -- 50% faster.
Given that the GUI can be pretty sluggish on the Pogo (but still certainly usable if you don't change things often), I nevertheless thought it might be cool to replicate my Pogo set-up on the Dockstar to see just how much faster it might be. (fn2) This went swimmingly using the incrediblebackup and incrediblerestore scripts: I was able to clone the Pogo to the Dockstar with no issue.
I suppose I could use a stopwatch to time things like an asterisk reload or a trunk revision. But I'd rather see if anyone is aware of any benchmarking programs/software that I could use on these ARM5 machines to see (just for fun) if the Dockstar's 50% clock-speed advantage translates into anything remotely like that in tests.
______________________
(fn1: My Dockstar, first put online in early 2011, has had a series of 'U-Boot' installations. Even though it has a Kirkwood ARM5 proc. like the Pogo, I'd had a number of problems booting the I-PBX Image. It turns out that my older U-Boot did not nicely support the 3.14.X kernel of the Pogo image. So, I finally updated the Dockstar to a U-Boot from 7-2014 which made the problem go away.)
(fn2: I used the Dockstar way-back-when, first compiling asterisk on the device and adding native FreePBX, based on advice from user twinclouds and others found in myriad forums -- mostly the Jeff Doozan forum. I moved away from it because I was changing things constantly, prompting me to move to a bare-metal cast-off PC and PIAF, then VMs, then the cloud, if for no other reason than the speed advantage. I'm older now, and tinker less, so going back to slower is fine. )
Given that the GUI can be pretty sluggish on the Pogo (but still certainly usable if you don't change things often), I nevertheless thought it might be cool to replicate my Pogo set-up on the Dockstar to see just how much faster it might be. (fn2) This went swimmingly using the incrediblebackup and incrediblerestore scripts: I was able to clone the Pogo to the Dockstar with no issue.
I suppose I could use a stopwatch to time things like an asterisk reload or a trunk revision. But I'd rather see if anyone is aware of any benchmarking programs/software that I could use on these ARM5 machines to see (just for fun) if the Dockstar's 50% clock-speed advantage translates into anything remotely like that in tests.
______________________
(fn1: My Dockstar, first put online in early 2011, has had a series of 'U-Boot' installations. Even though it has a Kirkwood ARM5 proc. like the Pogo, I'd had a number of problems booting the I-PBX Image. It turns out that my older U-Boot did not nicely support the 3.14.X kernel of the Pogo image. So, I finally updated the Dockstar to a U-Boot from 7-2014 which made the problem go away.)
(fn2: I used the Dockstar way-back-when, first compiling asterisk on the device and adding native FreePBX, based on advice from user twinclouds and others found in myriad forums -- mostly the Jeff Doozan forum. I moved away from it because I was changing things constantly, prompting me to move to a bare-metal cast-off PC and PIAF, then VMs, then the cloud, if for no other reason than the speed advantage. I'm older now, and tinker less, so going back to slower is fine. )