Jump to content

User:Esigc/sandbox

From Wikipedia, the free encyclopedia
< User:Esigc
This is an old revision of this page, as edited by Esigc (talk | contribs) at 16:32, 2 November 2024 (New citations show notability of topic. Rewrite also shows notability of topic. COI added. Outdated links removed. ~~~~). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
GlowCode
Developer(s)Electric Software Inc.
Initial release1997 (1997) by Electric Software Inc.
Stable release
10.0 / April 26, 2016; 9 years ago (2016-04-26)
Available inEnglish
LicenseProprietary
Websiteglowcode.com

GlowCode is a performance and memory/resource profiler developed by Electric Software Inc.[1]

Overview

GlowCode is used by software developers to analyze and optimize two main aspects of their application: performance (speed) and resource use.

Performance bottleneck detection is detailed, for example, in a description of how a team used GlowCode's "automated instrumentation of code ... to quickly identify the major time and scale sensitive components..." in their development of a cognitive analogical reasoner application.[2]

Another example of performance analysis can be seen in the function call tree output for a reconfigurable processor for a simultaneous localization and mapping system: "The results, captured with Glow Code, show that 83.3% of the algorithms time is spent in the filter update function. Looking deeper we targeted two other functions, gaussian_pose and motion_model_deadreck; these two functions compose the predict step in the algorithm and consume 39% of the application run time."[3]

GlowCode performance profiling is also discussed in books and journal articles such as "Writing Fast Programs" [4], "Traditional Techniques for Software Fault Localization.[5], and "A Survey of Performance Analysis Tools for OpenMP and MPI [6].

Detection of memory leaks and other resource usage problems is described, for example, in a paper detailing improvements of a graphical user interface (GUI) design, where "GlowCode provided a real-time peek at all the objects being used at a given time as well as a tally of the messages being passed back and forth between these objects"[7]. GlowCode also identifies resource problems specific to managed code, such as hyperactive and loitering objects.[8]

It is while the profiled application runs that GlowCode shows the duration, frequency and use of function calls, and identifies which functions play the most significant role in time-intensive tasks, which execution nodes are the source of multiple memory leaks, and which allocations are the source of excessive consumption of memory and resources.[9]

GlowCode profiles:

  • 64-bit and 32-bit code
  • Managed, native and mixed code
  • Code written in C, C++, C# or any .NET Framework-compliant language.[10]

GlowCode was launched in 1998.[11]

See also

References

  1. ^ "Performance profiler, memory leak detector for C++ C# .NET programmers and QA". GlowCode. Retrieved 2021-11-24.
  2. ^ Daily, Mike and Isdale, Jerry and Neely, Howard and Bogdanowicz, Julius (2009), Performance analysis of a cognitive analogical reasoner. 2009 IEEE Aerospace conference, pp. 1–8, doi:10.1109/AERO.2009.4839624, retrieved November 2, 2024{{citation}}: CS1 maint: multiple names: authors list (link)
  3. ^ Lycke, Roy and Li, Ji and Hamor, Ryan (2011), Investigation of a Reconfigurable Processor for a SLAM System (PDF), retrieved November 2, 2024{{citation}}: CS1 maint: multiple names: authors list (link)
  4. ^ Riley, John (2007), Writing Fast Programs: A Practical Guide for Scientists and Engineers, Cambridge: Cambridge International Science Publishing Ltd, p. 238, retrieved November 18, 2011
  5. ^ Yihao Li, Linghuan Hu, W. Eric Wong, Vidroha Debroy, Dongcheng Li (2023), Wong, Eric and Tse, T.H. (ed.), Traditional Techniques for Software Fault Localization, retrieved November 2, 2024{{citation}}: CS1 maint: multiple names: authors list (link)
  6. ^ Sairabanu, J. and Rajasekhara Babu, M. and Kar, Arunava and Basu, Aritra (2016). "A Survey of Performance Analysis Tools for OpenMP and MPI" (PDF). Indian Journal of Science and Technology. doi:10.17485/ijst/2016/v9i43/91712. Retrieved November 2, 2024.{{cite journal}}: CS1 maint: multiple names: authors list (link)
  7. ^ Jakuben, Benedict J. (2011), Improving Graphical User Interface (GUI) Design Using the Complete Interaction Sequence (CIS) Testing Method, retrieved November 2, 2024
  8. ^ GlowCode on Softpedia
  9. ^ "Dr. Dobbs Software Tools Newsletter", Dr. Dobb's Journal, 2002 (September), September 13, 2002, retrieved November 1, 2024
  10. ^ Dorsey, Terrence (July 2011), "Tools and Techniques for .NET Code Profiling", MSDN Magazine, 2011 (July), retrieved November 1, 2024
  11. ^ "New Products", Dr. Dobb's Journal, 1998 (July), July 1, 1998, retrieved November 1, 2024
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Esigc/sandbox&oldid=1254989145"