Live data from Hacker News

Highly efficient matrix transpose in Mojo

veitner.bearblog.dev

1–10 of 70 posts

Re: Highly efficient matrix transpose in Mojo

#2
I'm not an expert in this space, but is this meaningful? I'd assume that it's more common to fuse together transposition with an operation that precedes or follows it (e.g. matmul), which should be far more efficient than materializing the entire transposition in memory if it's just an intermediate value.

Re: Highly efficient matrix transpose in Mojo

#8
The "Switching to Mojo gave a 14% improvement over CUDA" title is editorialized, the original is "Highly efficient matrix transpose in Mojo".

Also, the improvement is 0.14%, not 14% making the editorialized linkbait particularly egregious.

Re: Highly efficient matrix transpose in Mojo

#9
post #8

The "Switching to Mojo gave a 14% improvement over CUDA" title is editorialized, the original is "Highly efficient matrix transpose in Mojo". Also, the improvement is 0.14%, not 14% making the editorialized linkbait particularly egregious.

0.14% is within the limits of statistical error. So this is a nothing-"article".

Re: Highly efficient matrix transpose in Mojo

#10
post #8

The "Switching to Mojo gave a 14% improvement over CUDA" title is editorialized, the original is "Highly efficient matrix transpose in Mojo". Also, the improvement is 0.14%, not 14% making the editorialized linkbait particularly egregious.

0.14% is within the limits of statistical error. So this is a nothing-"article".

[deleted]
Post reply on HN