Fetching the paper…
Reading the bibliography…
Properly benchmarking a system is a difficult and intricate task.
F. Yates, “Contingency tables involving small numbers and the
1934
Earlier work this paper cites.
P. J. Fleming and J. J. Wallace, “How not to lie with statistics: the correct way to summarize benchmark results,”
1986
Earlier work this paper cites.
L. W. McVoy, C. Staelin
1996
Earlier work this paper cites.
J. C. Mogul, “Brittle metrics in operating systems research,” in
1999
Earlier work this paper cites.
M. Seltzer, D. Krinsky, K. Smith, and X. Zhang, “The case for application-specific benchmarking,” in
1999
Earlier work this paper cites.
S. E. Sim, S. Easterbrook, and R. C. Holt, “Using benchmarking to advance research: A challenge to software engineering,” in
2003
Earlier work this paper cites.
K. Skadron, M. Martonosi, D. August, M. Hill, D. Lilja, and V. S. Pai, “Challenges in computer architecture evaluation,”
2003
Earlier work this paper cites.
M. Abadi, M. Budiu, U. Erlingsson, and J. Ligatti, “Control-flow integrity,” in
2005
Earlier work this paper cites.
S. Kurkowski, T. Camp, and M. Colagrosso, “MANET simulation studies: the incredibles,”
2005
Cited alongside, same era.
S. M. Bellovin, “On the brittleness of software and the infeasibility of security metrics,”
2006
Cited alongside, same era.
J. L. Henning, “SPEC CPU2006 benchmark descriptions,”
2006
Cited alongside, same era.
A. Traeger, E. Zadok, N. Joukov, and C. P. Wright, “A nine year study of file system and storage benchmarking,”
2008
Cited alongside, same era.
B. Krishnamurthy and W. Willinger, “What are our standards for validation of measurement-based networking research?”
2008
Cited alongside, same era.
S. Nagarakatte, J. Zhao, M. M. Martin, and S. Zdancewic, “Softbound: Highly compatible and complete spatial memory safety for C,” in
A. J. Aviv and A. Haeberlen, “Challenges in experimenting with botnet detection systems,” in
2011
Later among the works it cites.
I. Kuz, Z. R. Anderson, P. Shinde, and T. Roscoe, “Multicore OS benchmarks: We can do better,” in
2011
Later among the works it cites.
C. Rossow, C. J. Dietrich, C. Grier, C. Kreibich, V. Paxson, N. Pohlmann, H. Bos, and M. Van Steen, “Prudent practices for designing malware experiments: Status quo and outlook,” in
2012
Later among the works it cites.
M. Schwarzkopf, D. G. Murray, and S. Hand, “The seven deadly sins of cloud computing research,” in
2012
Later among the works it cites.
L. Szekeres, M. Payer, T. Wei, and D. Song, “Sok: Eternal war in memory,” in
2013
Later among the works it cites.
alphaXiv searches the wider corpus for related work and actual follow-ups.
alphaXiv is searching for related work…
2009
Cited alongside, same era.
T. Mytkowicz, A. Diwan, M. Hauswirth, and P. F. Sweeney, “Producing wrong data without doing anything obviously wrong!”
2009
Cited alongside, same era.
——, “Cets: Compiler enforced temporal safety for c,” in
2010
Cited alongside, same era.
G. Heiser, “Systems benchmarking crimes,”
Cited in the paper.
“byte-unixbench,”
Cited in the paper.
Google, “Octane benchmark,”
Cited in the paper.
The Mozilla Foundation, “Dromaeo, javascript performance testing,”
Cited in the paper.
2015
Later among the works it cites.
S. Crane, C. Liebchen, A. Homescu, L. Davi, P. Larsen, A.-R. Sadeghi, S. Brunthaler, and M. Franz, “Readactor: Practical code randomization resilient to memory disclosure,” in
2015
Later among the works it cites.
C. Collberg and T. A. Proebsting, “Repeatability in computer systems research,”
2016
Later among the works it cites.