Forums - Performance and architecture details for FastCV routines?

2 posts / 0 new
Last post
Performance and architecture details for FastCV routines?
jdonald
Join Date: 9 Jan 14
Posts: 9
Posted: Fri, 2014-01-10 18:51

We have an Android service running on the Snapdragon platform where performance and power are of top concern. We are considering using FastCV to optimize portions of our algorithm. How we go about this depends on what FastCV can offer over what we already have or alternatives like OpenCL or RenderScript.

I have dug through the forums, but have been unable to find much detail on performance or the underlying architecture. Ideally we could have ways to estimate cycle counts, but for now I'd just settle just for knowing which processor the specific calls run on. From the list of routines on https://developer.qualcomm.com/docs/fastcv/api/group__image__processing.... roughly what proportion run on the DSP vs the GPU or CPU?

From an earlier post, I gather that FastCV does not provide access to the ISP. If most of these calls run on the CPU, then this may not provide much of an advantage over a NEON implementation. If the image-processing routines run on the Adreno GPU, we're likewise concerned that our service may hurt an application that it is serving due to GPU context-switching.

  • Up0
  • Down0
jeff4s Moderator
Join Date: 4 Nov 12
Posts: 106
Posted: Tue, 2014-01-14 14:49

Your comments are very insightful. We face many design constraints in developing a CV application. In FastCV you can use fcvSetOperationMode to select a mode of operation to alleviate some of the concerns. In general, FASTCV_OP_LOW_POWER mode will direct functions to DSP implementation. FASTCV_OP_PERFORMANCE mode will use the processor whose implementation is the fastest. 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.