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

how to measure vector load performance #15

Open
gzc1090 opened this issue Jul 23, 2024 · 1 comment
Open

how to measure vector load performance #15

gzc1090 opened this issue Jul 23, 2024 · 1 comment

Comments

@gzc1090
Copy link

gzc1090 commented Jul 23, 2024

Hi,
I find your benchmark to be very valuable. Do you have any good ideas or suggestions for testing the performance (throughput or latency) of various vector load instructions? I would like to explore the vector load performance on the K1 and K230.

Thanks

@camel-cdr
Copy link
Owner

Hi, I played around with adding the vector load/stores to the single instructions measurements, but I came to the conclusion that it would be more useful in a separate benchmark.

#12 has some measurements that show how different stride values perform. Ideally we'd measure something like that, with data from the different caches and from memory. I'm not sure how to properly do those measurements, though. This should probably also take into account different prefetch strategies.

For now you can look at the LUT4, and ascii to utf16/utf32, where indexed, strided and segmented loads are used in some of the implementations.

If you have suggestions please share them, I was planing to look at some memory measurements done on other ISAs, but I haven't gotten around to that yet.

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