Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"next" branch performance #27

Closed
JJZim opened this issue Apr 19, 2016 · 1 comment
Closed

"next" branch performance #27

JJZim opened this issue Apr 19, 2016 · 1 comment

Comments

@JJZim
Copy link

JJZim commented Apr 19, 2016

Hello,
I'm currently trying to use the version in "next" branch.
After using it a while it seems that the performance significantly decreased in comparison to the 0.0.6 release.

For example, on a machine with a Core i7 CPU and a X300 USRP I was able to easily run 8 channels in parallel. There were no (or negligible amount of) overflows ("O") or drops ("D") on the USRP/Host.
Now, after updating to the "next" branch (commit: 31ae25c), I get lots of drops on the host and, in addition, the tracking algorithm seems to perform worse than before which leads to no or only sporadic position fixes.

I'm using the multichannel X300 realtime config with 8 channels (4 on each subdevice), all set to GPS L1 tracking with PCPS acquisition.

Regards,
Jan

@JJZim JJZim changed the title "next" branch preformance "next" branch performance Apr 19, 2016
@carlesfernandez
Copy link
Member

That commit seems not related to receiver's performance, it's only executed when exiting the program. Please execute volk_profile and volk_gnsssdr_profile to take advantage of the best SIMD acceleration in your machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants