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: "a language based serverless function accelerator"
  Abstract: Serverless computing is an approach to cloud computing that allows programmers to run serverless functions in response to short-lived events. Cloud providers bill functions at sub-second granularity, provide transparent elasticity, and completely manage operating system resources. Unfortunately, today's serverless platforms exhibit high tail latency, because it is difficult to maximize resource utilization while minimizing operating costs. #R##N#We present Containerless, which is a serverless function accelerator that lowers the latency and resource utilization of typical serverless functions written in JavaScript. In Containerless, a serverless function starts execution in a container, and is instrumented to build an execution trace tree (similar to a tracing JIT compiler). After the function processes a number of events, Containerless extracts the trace tree, compiles it to safe subset of Rust, and then processes subsequent events more efficiently in Rust, using language-based sandboxing instead of the container sandbox. If the Rust code receives an event that triggers an unknown or unsupported execution path, Containerless aborts the language-based sandbox and restarts execution in the container. This approach works because serverless platforms already require functions to tolerate re-execution for fault tolerance. To a serverless function, a re-execution caused by Containerless is observationally equivalent to a re-execution caused by a fault. #R##N#Our evaluation shows that Containerless can significantly decrease the latency and resource utilization usage of serverless functions, e.g., increasing throughput of I/O bound functions by 3.4x (geometric mean speedup). We also show that the impact of tracing is negligible and that Containerless seamlessly switches between its two modes of sandboxing.

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.DC(Distributed, Parallel, and Cluster Computing)