Search

The article focuses on the performance improvements included in the Microsoft.NET Framework 4.5. The author mentions that the among the performance improvements in the .NET Framework 4.5 is found in its capability to handle multicore just-in-time (JIT) compilation, which is important in achieving better hardware-assisted performance. He adds that there are also improvements in several components including its parallel computing libraries (PCIs) and server garbage collection (GC).

The article focuses on the advantages and disadvantages of using asynchronous methods in programming. The author discusses how the Framework developers optimize object allocations and garbage collections when designing asynchronous methods. Particular focus is also given to the role of synchronization context in developing asynchronous methods.

The article presents an in-depth look into the large object heap in relation to the Common Language Runtime (CLR) garbage collector of Microsoft .NET Framework. It explores what qualifies an object as a large object, how these large objects are collected and what kind of performance implications large objects affect. In the Microsoft .NET Framework, an object that is greater or equal to 85,000 bytes is considered a large object. A discussion of the fundamentals of the .NET garbage collector is presented. Other topics covered include when garbage collection occurs, the large object heap (LOH) performance implications in the context of allocation costs, the collection of performance data for the LOH and the purpose of debugging.

Discusses strategies for managing the lifecycle of Remote.NET objects with leasing and sponsorship. Configuration of leasing applications; Design guidelines and options for leasing; Influence on computer programming and performance; Automation of the management of lease sponsors; Emphasis on the garbage collection concept to manage the lifecycle of objects in the Microsoft.NET framework.

Discusses the application of .NET Profiler application program interfaces in understanding garbage collection. Allocation of common language runtime; Collection of free memory for other programs; Consideration of global or static object pointer.

Discusses how to improve the real-time performance of garbage collection in computer systems. Definition of garbage collection; Generational garbage collection; Traditional mark and sweep garbage-collection algorithm; Incremental garbage collection.

Presents a question and answer advisory related to computer programming. Strategies of garbage collection JScript; Mechanisms of importing extensible markup language into a database; Design of search interface.

Focuses on the importance of garbage collection in embedded systems. Information on incremental and batch collectors; Advantages of the method called tracing; Functions of the ideal garbage collection algorithm for embedded systems.

The article provides information on the Common Language Infrastructure (C++/CLI). C++/CLI can be defined as an extension of the C++ programming language that provides features such as properties, events, garbage collection and generics for all types. In this article, the author examines C++ programs that are minimally ported to the new environment using managed extensions. The purpose is to determine whether the programs are susceptible to the buffer overflow vulnerabilities that have plagued C and C++ programs. The compiler generates Microsoft Intermediate Language when using managed extensions.

Provides information on the garbage collection capability of Java program language. Special cases where memory management must be handled by the application; Description of object pooling; Web applications of caching and pooling; Design aspects the caching and pooling shares; Description of writing memory-management code.

Presents information on a study which described the use of garbage pooling in reducing the number of garbage collection executions in a Java application. Advantages and disadvantages of C++ garbage-collected approaches; Execution time of the garbage collector; Information on the ObjectPool class; Conclusions.

Examines several incremental memory-management algorithms. Reference counting algorithm; Practical concerns for a performance-oriented C/C++ collector; Factors that posed challenges for any allocator.

Discusses the advantages of using the Java computer programming language to leaks in computer memory. Dynamics of memory management in Java; Myths about garbage collection in Java; Conclusion.

This article focuses on the BuDDy library that allows the implementation and manipulation of Boolean expressions. The library exposes a Binary Decision Diagram interface rather than a Boolean expression interface. BuDDy is implemented in C but has a wrapping C++ interface. It has an internal garbage collection mechanism optimizing its memory usage, totally transparent if one decides to use the C++ interface. BuDDy also has a cache that saves the last results of operations. Almost everything performance related is configurable through the interface, and the library begins running with default values, so one can start using it without being familiar with all the possible configurations. BuDDy has a rich set of operations, which can help implement very complex operations with only a few code lines. Among the operations in the interface are the abilities to define the variables of the expressions one is going to create, refer a large vector of binary variables as a vector of encoded integers and create a vector of expressions. The manipulation operation includes the ability to perform various kinds of Boolean operations on one or more expressions and vector-oriented operations on vectors of expression, referring to them as encoded integer.

This article reports that researchers at International Business Machines Corp. (IBM) have developed a real-time Java platform that includes a garbage collector with claimed worst-case delays of 2 milliseconds. IBM's Metronome technology is being tested by an unnamed customer in the defense sector, with a public detailing of the work expected in a month or so. Garbage collection frees up dynamically allocated memory that is no longer referenced by an application, but it should not interfere when the system is called upon to respond immediately. Perry Cheng, a staff researcher at IBM's Watson lab, said that IBM's approach makes real-time programming in Java easier because its real-time garbage collector is fast enough for most applications.

This article focuses on Niklaus Wirth's development of Oberon in Zurich, Switzerland. According to Wirth, Oberon evolved from a project whose goal was the design of a modern, flexible and efficient operating system (OS) for a single-user workstation. The OS was initially designed in Modula-2, but Wirth felt that because Modula-2 allowed the use of variant record types, garbage collection would be difficult. Consequently he decided to design a new language that would provide other methods for extending record types. Wirth also wished to experiment with a minimalist approach to language design that emphasized mathematical purity. As a result, Oberon evolved from Modula-2 chiefly by subtracting features from Modula-2, although some new features were added. Some of the subtracted features include variant records, opaque data types, enumeration types, subrange types, reserved words CARDINAL and WITH, local modules. Although Oberon may not reach the same levels of commercial acceptance as Wirth's Pascal and Modula-2, it has already influenced designers of subsequent languages. Modula-3 was designed to provide OO extensions to Modula-2 as well as support for threads, exceptions and garbage collection.

Lists several Web sites that offer information on graphical user interfaces (GUI) and books that might be useful in learning about garbage collection and how it can be used with Java and embedded systems.

The article discusses the WebLogic RealTime (WLRT) 1.1, a new software solution developed by BEA Systems Inc. WLRT is composed of an optimized WebLogic application server and the JRockit Java Virtual Machine, and it supports applications that demand fast, predictable response times and low latency. It lessen the latency brought by garbage collection and provides better performance regardless of whether the application is Java or JavaEE executing in a third-party container. Moreover, WLRT is designed to help the developers and information technology (IT) administrators meet the needs of mission critical enterprise Java deployments, increase productivity and reduce IT project costs.

The article highlights the topics discussed during the 2004 ISO C++ Standards meeting in Redmond, Washington from October 17 to 22. The final technical changes were voted into the Library extensions technical report, and this batch of extensions to the C++ Standard Library has been completed. This batch of extensions includes support for pointers, hash-based containers, type traits, random number generators, expressions, tuple types, a function wrapper and a slew of mathematical functions. The Evolution Working Group has worked through proposals. Here are some of the proposals that are likely to come up for vote. These are the C99 long long, fixing right angle brackets, a static assert facility for compile-time assertions, nullptr as a spelling for the null pointer value, enumerations, extended friend support and adopting C99 preprocessor extensions. The Evolution Working Group was organized into three groups. First, support for library building. This will focus on areas pertinent to building libraries in C++, including better support for generic programming. Second, modularity and libraries. This will focus on standardizing support for libraries and to provide a module system in C++. Third, safety, regularity and performance which focus on issues including security, threading and garbage collection. Under the Library Working Group, support for novices and incidental programmers was initiated. This area concentrates on providing simplification via libraries.