Live data from Hacker News

Apple Neural Engine: Architecture, Programming, and Performance

arxiv.org

11–20 of 30 posts

Re: Apple Neural Engine: Architecture, Programming, and Performance

#13
post #6

This scans very much as AI-written.

This is obvious Claude slop writing, the author would be advised to use vale [1] with samples of their own writing as a guide. > Performance begins with the roofline. On the M1 the engine holds about 12 fp16 TFLOP/s of compute against a DRAM-bandwidth ceiling. The roofline has a ridge point near 141 FLOP per byte, a 2 MB working-set threshold, a 0.23 ms floor under any single dispatch, and efficiency near 0.37 picojo…

Please no. The author would be advised to write their own original thoughts.

Re: Apple Neural Engine: Architecture, Programming, and Performance

#14
post #13
post #6

Earlier quoted context omitted.

This is obvious Claude slop writing, the author would be advised to use vale [1] with samples of their own writing as a guide. > Performance begins with the roofline. On the M1 the engine holds about 12 fp16 TFLOP/s of compute against a DRAM-bandwidth ceiling. The roofline has a ridge point near 141 FLOP per byte, a 2 MB working-set threshold, a 0.23 ms floor under any single dispatch, and efficiency near 0.37 picojo…

Please no. The author would be advised to write their own original thoughts.

It was a joke, nothing could save this "paper". I don't think the author wrote anything. They pointed claude at a directory and said "write a paper"

Re: Apple Neural Engine: Architecture, Programming, and Performance

#18
post #7

Earlier quoted context omitted.

The burden of proof should be with the beholder. Must be so easy to scream AI when you don’t want to read an article.

You obviously haven't read it, because it is clunky garbage. > 19.4 Pacing compiles after a failure > A failed compile is not free of side effects on the shared compile service. A compile that fails restarts the service, which takes a few seconds to come back, and failures that keep arriving faster than the service can restart between them keep it from making progress, so unrelated compiles slow down until the failur…

Personally I'm not in the habit of printing and eating articles I read, but in the unlikely event that I did I find it even less likely that I would be concerned with its' nutritional content. (/s)

Re: Apple Neural Engine: Architecture, Programming, and Performance

#20
post #7

Earlier quoted context omitted.

The burden of proof should be with the beholder. Must be so easy to scream AI when you don’t want to read an article.

You obviously haven't read it, because it is clunky garbage. > 19.4 Pacing compiles after a failure > A failed compile is not free of side effects on the shared compile service. A compile that fails restarts the service, which takes a few seconds to come back, and failures that keep arriving faster than the service can restart between them keep it from making progress, so unrelated compiles slow down until the failur…

you forgot the bologna and iceberg lettuce
Post reply on HN