Shell Scripts (8 concurrent) 546.7 lpm (60.1 s, 2 samples) Shell Scripts (1 concurrent) 4243.2 lpm (60.1 s, 2 samples) Process Creation 6001.9 lps (30.0 s, 2 samples) Pipe-based Context Switching 137562.2 lps (10.0 s, 7 samples) Model name : Intel(R) Xeon(R) CPU L5520 2.27GHzĪddress sizes : 40 bits physical, 48 bits virtual System Call Overhead 15000.0 564591.2 376.4įor grins, here is a comparison run of my bottom-dollar Cloud at Cost IPBX 12 instance, obtained while running all of the IPBX-related programs and daemons, as well as rTorrent: System Call Overhead 564591.2 lps (10.0 s, 7 samples) Shell Scripts (8 concurrent) 102.1 lpm (60.5 s, 2 samples) Shell Scripts (1 concurrent) 825.7 lpm (60.1 s, 2 samples) Process Creation 1401.6 lps (30.0 s, 2 samples) Pipe-based Context Switching 15723.0 lps (10.0 s, 7 samples) Model name : Feroceon 88FR131 rev 1 (v5l)įilesystem 1K-blocks Used Available Use% Mounted onġ CPU in system running 1 parallel copy of testsĭhrystone 2 using register variables 2004541.1 lps (10.0 s, 7 samples)ĭouble-Precision Whetstone 44.3 MWIPS (9.9 s, 7 samples)Įxecl Throughput 488.5 lps (29.8 s, 2 samples)įile Copy 1024 bufsize 2000 maxblocks 81096.5 KBps (30.0 s, 2 samples)įile Copy 256 bufsize 500 maxblocks 27275.7 KBps (30.0 s, 2 samples)įile Copy 4096 bufsize 8000 maxblocks 159421.5 KBps (30.0 s, 2 samples) I'm older now, and tinker less, so going back to slower is fine.
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. (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. So, I finally updated the Dockstar to a U-Boot from 7-2014 which made the problem go away.) It turns out that my older U-Boot did not nicely support the 3.14.X kernel of the Pogo image. like the Pogo, I'd had a number of problems booting the I-PBX Image.
(fn1: My Dockstar, first put online in early 2011, has had a series of 'U-Boot' installations. 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. I suppose I could use a stopwatch to time things like an asterisk reload or a trunk revision. (fn2) This went swimmingly using the incrediblebackup and incrediblerestore scripts: I was able to clone the Pogo to the Dockstar with no issue. 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. 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. (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. I finally got around to tweaking my old Dockstar so that it handles the I-PBX image (see ) more gracefully.