Demo Data from SIGIR 2026 / reviewers in the wild / expert
Tohru Nishigaki
dblp:87/839
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 1983
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Performance modeling and evaluation · 100% | |
| Software engineering, system software, and programming languages
1 paper |
Operating systems · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Performance modeling and evaluation › workload characterization
program behavior |
0.0 | 1 | 1983 | Experiments on the Knee Criterion in a Multiprogrammed Computer System · IEEE Trans. Software Eng. 1983 |
Performance modeling and evaluation
workload characterization |
0.0 | 1 | 1983 | Experiments on the Knee Criterion in a Multiprogrammed Computer System · IEEE Trans. Software Eng. 1983 |
Operating systems › resource management › memory management
page replacement |
0.0 | 1 | 1983 | Experiments on the Knee Criterion in a Multiprogrammed Computer System · IEEE Trans. Software Eng. 1983 |
Operating systems › resource management › memory management
virtual memory |
0.0 | 1 | 1983 | Experiments on the Knee Criterion in a Multiprogrammed Computer System · IEEE Trans. Software Eng. 1983 |
Methods — techniques the papers use, named apart from their topics
knee criterion analysis · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1983 | Experiments on the Knee Criterion in a Multiprogrammed Computer SystemabstractAlthough the effectiveness of the knee criterion [7] as a virtual memory management strategy is widely accepted, it has been impossible to take advantage of it in a practical system, because little information is available about the program behavior of executing jobs. Tohru Nishigaki |
IEEE Trans. Software Eng. | 1 |