| > Please hold off on replying further on this thread until you have read OP's linked paper. This continues the holier-than-thou attitude, but also violates this site's rules. Not only I have read the entire court transcript, I was following it with interest as it happened. My point still stands. It is sleazy, to say the least, to misquote the whistleblower. It is even more sleazy to base such quote on "something the defendant claimed that the plaintiff claimed in a civil lawsuit". This is point #1 on this "critique" and already rings all alarm bells, which is what my comment was about. Google also did many, many evils during the entire trial (e.g. through the entire SLAPP thing) that no wonder they did not want to expose to the public. But that's another story. > How large do you imagine the conspiracy is here? Not large. Google continuously publishes papers where the results cannot be reproduced, at least by the time the paper is published, and barely gets a slap on the wrist from Nature, which is supposed to enforce these things. > The method is secretly bad, but the TPU team uses it in production anyway? MediaTek built on it anyway? The TF-Agents team claimed to reproduce it, but they're actually lying? Neither Tensor nor Mediatek are examples of really high-stages design; Tensor is not know for beating any records and Mediatek specializes in value. While my area is frontend rather than backend, I have a passing familiarity with automatic macro placement (due to the fact that the barriers between flow steps keep getting thinner every day). Almost every other chip house of large-enough size has a macro placer. Almost every PhD student has implemented one. It's an easy problem, and with minimal knowledge about your design style you can likely do a better job than the generic ones from major vendors. However, it doesn't matter if you have the best macro placement engine in the world, your results would still not be ground-breaking overall. You can in fact ALSO do a terrible job and still get a pretty decent result since the flow will compensate. This was already my informed opinion even before the Nature article, but for Google's method, which _requires_ another placement tool to refine its work, would be even more true. And Google's method even requires a GPU farm for something that is, while important, still a relatively short step in the entire placement flow (and for not very push-through performance designs like Google's or MediaTek's , which are like the bread and butter of the world, the entire flow would not have required GPUs before). It's no wonder than the whistleblower thought the entire point of this Nature article was for Google to sell more Google Cloud GPU time. They may have convinced Mediatek, but not the academic community. |