In his presentation "Understanding Hardware Transactional Memory" at QCon New York 2016, Gil Tene introduces hardware transactional memory (HTM). Whereas the concept of HTM is not new, it is now finally available in commodity hardware. The purpose of HTM is to be able to write to multiple addresses in memory in an atomical way so that there cannot be inconsistencies in cooperation other threads.
As announced at CppCon, Bjarne Stroustrup and Herb Sutter have started working on a set of guidelines for modern C++. The goal of this effort is improving how developers use the language and help ensuring they write code that is type safe, has no resource leaks, and is as much as possible free of programming logic errors.
Mobile Backend as a Service provider AnyPresence continues to hone their chops. Launching the fifth update to their self-titled platform geared for the enterprise. Co-founder Rich Mendis provides some insights for InfoQ readers…
Visual Studio 2013 comes with a better memory profiler for .NET applications, but it is still far behind the other commercial offerings.
.NET 4.5 brings with it a generic version of WeakEventManager for WPF developers. In addition to not needing the event-specific subclass, this version also dispenses with the need for listener interfaces.
Windows Presentation Foundation is quickly becoming well known for the ease in which memory leaks are introduced. Most of these leaks seem to come from the use or misuse of weak references, upon which WPF’s data binding technology is based. In the recent set of hotfixes many of these leaks are fixed.
Fabrice Marguerie, a software architect and consultant, wrote the article How to detect and avoid memory and resources leaks in .NET applications, published on MSDN. The article explains how memory and resource leaks can happen while programming for .NET and how to avoid them.
WPF, also known as Windows Presentation Foundation, represents the future of UI on the Windows platform. And if Microsoft has its way, its younger sibling Silerlight will take over the web and mobile markets. But like any new technology, it has some issues to work through including some rather serious memory leaks.
Microsoft is planning some simple but much welcomed performance improvements for the core System.IO functionality. These include convenience methods for reading and writing text-based files, significantly faster directory enumeration, and support for memory mapped files.
Gemstone has released Gemfire Enterprise 6.0 featuring a cluster resource controller that continuously monitors resources in the distributed data fabric. GemFire enables applications to sense changing performance patterns and proactively provision extra resources and trigger rebalancing of predictable data access, throughput, and latency without the need to overprovision capacity.
In this talk from RubyFringe, Tom Preston-Werner talks about how he uses the scientific method for tracking down software problems. He demonstrates how he used this approach to track down a particularly sneaky memory leak in a Ruby app, and more.
Quest Software recently released JProbe 8.0, a Java code, memory, and coverage profiler. While JProbe has been one of the leading Java profiling tools since the late 1990's, JProbe 8.0 aims to help Quest regain the leadership position in the profiling market with new Eclipse integration and a more competitive price point.
Steven Haines from Quest has published an article demonstrating the use of performance analysis tools in the continuous build cycle as best practice and makes some thought provoking points about the cost of not doing so.