human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "oltp on hardware islands"
  Abstract: Modern hardware is abundantly parallel and increasingly heterogeneous. The numerous processing cores have non-uniform access latencies to the main memory and to the processor caches, which causes variability in the communication costs. Unfortunately, database systems mostly assume that all processing cores are the same and that microarchitecture differences are not significant enough to appear in critical database execution paths. As we demonstrate in this paper, however, hardware heterogeneity does appear in the critical path and conventional database architectures achieve suboptimal and even worse, unpredictable performance. We perform a detailed performance analysis of OLTP deployments in servers with multiple cores per CPU (multicore) and multiple CPUs per server (multisocket). We compare different database deployment strategies where we vary the number and size of independent database instances running on a single server, from a single shared-everything instance to fine-grained shared-nothing configurations. We quantify the impact of non-uniform hardware on various deployments by (a) examining how efficiently each deployment uses the available hardware resources and (b) measuring the impact of distributed transactions and skewed requests on different workloads. Finally, we argue in favor of shared-nothing deployments that are topology- and workload-aware and take advantage of fast on-chip communication between islands of cores on the same socket.

Connected through hyperedge HE-1 (induced by source paper "towards concurrent stateful stream processing on multicore processors technical report"):
  with members:
    - "briskstream scaling data stream processing on shared memory multicore architectures"
    - "s store streaming meets transaction processing"

Connected through hyperedge HE-2 (induced by source paper "briskstream scaling data stream processing on shared memory multicore architectures"):
  with members:
    - "r storm resource aware scheduling in storm"

Connected through hyperedge HE-3 (induced by source paper "scaling stream processing with transactional state management on multicores"):
  with members:
    - "scheduling storms and streams in the cloud"

Connected through hyperedge HE-4 (induced by source paper "reactors a case for predictable virtualized actor database systems"):
  with members:
    - "optimization of imperative programs in a relational database"
    - "transactional partitioning a new abstraction for main memory databases"
    - "design principles for scaling multi core oltp under high contention"
    - "warp lightweight multi key transactions for key value stores"
    - "elastras an elastic transactional data store in the cloud"

Connected through hyperedge HE-5 (induced by source paper "design principles for scaling multi core oltp under high contention"):
  with members:
    - "the homeostasis protocol avoiding transaction coordination through program analysis"
    - "rethinking serializable multiversion concurrency control"
    - "automatic partitioning of database applications"
    - "high performance concurrency control mechanisms for main memory databases"
    - "flat combining and the synchronization parallelism tradeoff"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.DB(Databases)