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.

Sign up for GitHub

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

Jump to bottom

Optimize caching on trig functions #16

Open
GoogleCodeExporter opened this issue Jun 28, 2015 · 0 comments
Open

Optimize caching on trig functions #16

GoogleCodeExporter opened this issue Jun 28, 2015 · 0 comments
Labels
auto-migrated Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

Currently the trig functions store the keys/values separately (as pointed out 
by Tev). For cache optimization reasons it makes sense to store the key and 
values next to each other so that they can be fetched from the same cache line 
in a single operation.

Original issue reported on code.google.com by Flatmush@googlemail.com on 23 Jul 2012 at 9:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter