|
发表于 2014-12-18 10:04:47
|
显示全部楼层
本帖最后由 alayi 于 2014-12-18 10:11 编辑
墙外看到的,有人在M4上试过,貌似有难度
http://lists.xiph.org/pipermail/opus/2014-November/002725.html
However now that we're doing a first implementation on M4, we're seeing
significantly higher cycle counts -- more in the range of 100 MHz of CPU
needed to encode with the same parameters. Additionally, compared to
1.0.3, the code size and data size of the Opus codec in 1.1 has
increased significantly (which makes it a challenge to fit in the on-SoC
SRAM of the M4).
Obviously we need to use the ARM ASM that landed in -beta, and we can
decrease the complexity to somewhat reduce the CPU utilization, but I'm
wondering if I'm missing any other low-hanging fruit in optimizing Opus
for this target CPU. I haven't even started to do code profiling or CPU
performance counter analysis.
Does anyone have examples of similar applications? What kinds of CPU
occupancy have other people seen on similar CPUs? Do we need to get
some NEON asm? Does anybody have spare cycles to take paid work in this
space? |
|