Unlike some fields, Computer Science has had a long, friendly, and synergistic relationship between industry and academia. For example, when I started going to the International Symposium on Computer Architecture (ISCA) in the 1970s, 40% of the papers were on real products from industry.
Alas, industry papers fell from 40% in the 1970s to 10% recently at ISCA, and even that 10% includes papers based more on industrial research rather than on industrial products. If these trends continue, the historically strong bond between computer architecture research and practice could fade, making it harder to understand the problems facing industry and for our research to have impact. When I complained at ISCA 2019 about the lack of papers on real industrial products, ACM SIGARCH chair Sarita Adve overheard and assigned me to help fix the problem for 2020.
I thought the only hope was a separate submission process with a separate program committee (PC) whose members believed that retrospective papers on industrial products were valuable complements to academic research papers. The PC members also must understand that company concerns about patent issues or trade secrets may mean some details are not revealed. We tried the following guidelines for industry papers, which has many differences from regular ISCA and other conferences that have industry tracks:
The competition was stiff for the 19 papers we received (3 recruited), with the majority of papers being strong. They were so strong that Sophia Shao and I are guest editing a special issue of IEEE Micro for the papers that we couldn't accept. PC members who were also on the regular ISCA PC found that the industry papers were very engaging and brought interesting perspectives with different values than the typical ISCA submission. We accepted 5/19 or 26%, only one was recruited (the regular ISCA PC accepted 77/428 or 18%). Each paper proudly bore the label "Industrial Product."
I was delighted the papers appeared in the honored first session of ISCA. The big question was the ISCA audience reaction. The graph shows the main survey question about the industry track (132 responses). I'm not sure what other questions would get 80% agreement from the traditionally skeptical computer architects—free alcohol and ice cream at the ISCA reception? Given the many changes we tried, I was thrilled with these results.
In retrospect, I suspect that few of the selected papers would have survived the traditional ISCA process, as reviewers would expect different content and evaluations, so I believe a separate PC is critical to the success of an industry session. I think that restricting papers to be on real products by actual industry authors is what made attendees say the ISCA program was stronger and more exciting than ISCAs of the recent past. The small PC led to much more thorough discussions than a typical PC meeting and the delayed deadline increased our submissions. We intend to follow all six guidelines above in the future.
perhaps more conferences should consider these guidelines and institute an industry track?
David Patterson is a Google distinguished engineer; a professor for the Univesity of California, Berkeley; RISC-V International Vice Chair, and the RISC-V International Open Source (RIOS) Laboratory Director. His newest book is The RISC-V Reader: An Open Architecture Atlas and his best known is Computer Architecture: A Quantitative Approach. He and his co-author John Hennessy shared the 2017 ACM A.M. Turing Award.
Thanks David, for your article on this important topic. I agree with all you say (a standard I don't achieve with even my own writings). From my experience, having been an ACM member since 1973, the connection between academe and industry has monotonically declined to a very sad state. I applaud efforts to reverse the trend; yours being an excellent role model that I hope will inspire others.
Displaying 1 comment