About: Resource management (computing) is a research topic. Over the lifetime, 793 publications have been published within this topic receiving 10838 citations.
TL;DR: The prototype exokernel system implemented here is at least five times faster on operations such as exception dispatching and interprocess communication, and allows applications to control machine resources in ways not possible in traditional operating systems.
Abstract: Traditional operating systems limit the performance, flexibility, and functionality of applications by fixing the interface and implementation of operating system abstractions such as interprocess communication and virtual memory. The exokernel operating system architecture addresses this problem by providing application-level management of physical resources. In the exokernel architecture, a small kernel securely exports all hardware resources through a low-level interface to untrusted library operating systems. Library operating systems use this interface to implement system objects and policies. This separation of resource protection from management allows application-specific customization of traditional operating system abstractions by extending, specializing, or even replacing libraries. We have implemented a prototype exokemel operating system. Measurements show that most primitive kernel operations (such as exception handling and protected control transfer) are ten to 100 times faster than in Ultrix, a mature monolithic UNIX operating system. In addition, we demonstrate that an exokernel allows applications to control machine resources in ways not possible in traditional operating systems. For instance, virtual memory and interprocess communication abstractions are implemented entirely within an application-level library. Measurements show that application-level virtual memory and interprocess communication primitives are five to 40 times faster than Ultrix's kernel primitives. Compared to state-of-the-art implementations from the literature, the prototype exokernel system is at least five times faster on operations such as exception dispatching and interprocess communication.
TL;DR: In this article, a method and a computer architecture monitoring resource usage via a global computer network is proposed, which includes a resource-metering data recorder/translator unit having a global network node and, in operation, recording resource usage measured by and associated resource meter.
Abstract: A method and computer architecture monitoring resource usage via a global computer network. The computer architecture may include a resource-metering data recorder/translator unit having a global computer network node and, in operation, recording resource usage measured by and associated resource meter. The computer architecture further includes a database and at least one global computer network server, in operation, storing resource usage data recorded by the data recorder/translator unit in the database, receiving a resource usage data query from a user, calling the database for resource usage data relevant to the user, and presenting resource management information based on the relevant resource usage data via a global computer network site to the user. The computer architecture may also include a resource-metering data recorder, in operation, recording resource usage data measured by an associated resource meter, and also includes a recorder translator, in operation calling the data recorder, and transferring the resource usage data from the data recorder to the database.
TL;DR: In this article, an integrated remote execution system manages resources and provides for the distributed and remote execution of remote requests to those resources in a heterogeneous computer network environment that has a plurality of resources loosely coupled to each other.
Abstract: An integrated remote execution system manages resources and provides for the distributed and remote execution of remote requests to those resources in a heterogenous computer network environment that has a plurality of resources loosely coupled to each other. The resources include at least two or more computer processors executing different operating system programs and any memory devices and subordinate programs operating together with the computer processors. Three major components are integrated into a single system by providing for a common remote execution interface that is incorporated into the requesting application program to provide a single programming interface for making remote requests to the system, a separate resource management component to provide information about the various resources in the network, and a remote service routine that can be executed on any of the computer processors selected perform the remote request. The remote execution interface can have the user to determine the selection of which resources to use, or it can automatically make the selection of which resources to use. The resource management component utilizes a hybrid model for managing resources in the network that includes a resource information database that is publish-based and a query module that is query-based. The remote service routine receives the remote requests from the remote execution interface which initiated the remote request and forks a separate remote execution control process for each remote request that actually initiates and performs the remote service in response to the remote request.
TL;DR: High Performance Cluster Computing: Programming and Application Issues, Volume 2, Rajkumar Buyya brings together the world's leading work on programming and applications for today's state-of-the-art "commodity supercomputers".
Abstract: From the Publisher:
A comprehensive guide to today's most advanced R&D in highly parallel programming and applications.
Volume 1 of this two-volume set collected today's best work on the systems aspects of high performance cluster computing. Now, in High Performance Cluster Computing: Programming and Application Issues, Volume 2, Rajkumar Buyya brings together the world's leading work on programming and applications for today's state-of-the-art "commodity supercomputers."
The book is organized into three areas: programming environments and development tools; Java(tm) as a language of choice for development in highly parallel systems; and state-of-the-art high performance algorithms and applications. All three areas have seen major advances in recent years-and in all three areas, this book offers unprecented breadth and depth. Coverage includes:
New parallel programming techniques and tools, including MP and PVM, active objects, scoped behavior, and LiPS.
State-of-the-art debuggng techniques: Code liberation, global renaming, name reclamation, and debugging interfaces.
The WebOS: Designing operating system services for wide-area applications.
Leveraging Java(tm) to the fullest: Distributed objects, the HPspmd model, and more.
Clustered Web servers and other high performance Web applications.
Real-time resource management, climate ocean modeling, parallel reflexive reasoning, content-based image retrieval, biomedical applications, and more.
TL;DR: An inclusive taxonomy for architectural, algorithmic and technologic aspects of fog computing is provided and base architectures for application, software, security, computing resource management and networking are presented and evaluated using a proposed maturity model.
Abstract: Fog computing is an emerging technology to address computing and networking bottlenecks in large scale deployment of IoT applications. It is a promising complementary computing paradigm to cloud computing where computational, networking, storage and acceleration elements are deployed at the edge and network layers in a multi-tier, distributed and possibly cooperative manner. These elements may be virtualized computing functions placed at edge devices or network elements on demand, realizing the “computing everywhere” concept. To put the current research in perspective, this paper provides an inclusive taxonomy for architectural, algorithmic and technologic aspects of fog computing. The computing paradigms and their architectural distinctions, including cloud, edge, mobile edge and fog computing are subsequently reviewed. Practical deployment of fog computing includes a number of different aspects such as system design, application design, software implementation, security, computing resource management and networking. A comprehensive survey of all these aspects from the architectural point of view is covered. Current reference architectures and major application-specific architectures describing their salient features and distinctions in the context of fog computing are explored. Base architectures for application, software, security, computing resource management and networking are presented and are evaluated using a proposed maturity model.