It's UWAweek 47

help5507

This forum is provided to promote discussion amongst students enrolled in CITS5507 High Performance Computing.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying the 4 articles in this topic
Showing 4 of 148 articles.
Currently 22 other people reading this forum.


 UWA week 43 (2nd semester, study break) ↓
SVG not supported

Login to reply

👍?
helpful
5:16pm Thu 24th Oct, ANONYMOUS

Hi, We are conducting tests on our laptop, and I have observed that when running the program locally, the bottleneck for matrix multiplication shifts from the CPU to the memory. Saying when the size of the matrices exceeds 50000, dynamic memory allocation results in a bad_alloc error. But all of these can be easily done in 10 minutes. In this case, how should we implement our experiment? Thanks for your reply.


SVG not supported

Login to reply

👍x1
helpful
12:53pm Fri 25th Oct, Marcell S.

This might happen depending on how much memory you have on your laptop. This is perfectly fine -- you'll simply have to explain this observation in your report. You can still talk about how your implementation scales below these values, and then explain that you are running out of memory when exceeding N=50,000.


SVG not supported

Login to reply

👍?
helpful
2:15pm Fri 25th Oct, ANONYMOUS

My current idea is to reduce the time limit from ten minutes to one minute. This way, I can make full use of the experimental data I have obtained. Is that okay?


SVG not supported

Login to reply

👍?
helpful
5:39pm Fri 25th Oct, Marcell S.

If you have some one minute experiments from Setonix, you can use other one minute experiments for comparison. But you should try to do longer experiments (i.e. 10 minutes) where you can.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy