Posts Tagged ‘google’
April 8th, 2010 | 
Author: 
Google Tech Talks
June 13, 2007
ABSTRACT
Liane Praza, the tech lead on Solaris Service Management Facility will talk about the current and future plans for SMF.
The Service Management Facility has improved several aspects of the Solaris administrative model. Some of the most notable updates are:
* Services are represented as first-class objects that can be viewed (using the new svcs(1) command) and managed (using svcadm(1M) and svccfg(1M)).
* Failed services are automatically restarted in dependency order, whether they failed as the result of administrator error, software bug, or were affected by an uncorrectable hardware error.
* More information is available about misconfigured or…
Duration : 0:54:31
Google TechTalks
March 8, 2006
Jim whitehead
Jim Whitehead is an Assistant Professor of Computer Science at the University of California, Santa Cruz. He has recently been developing a new degree program on computer gaming, the BS in Computer Game Engineering. Jim received his PhD in Information and Computer Science from UC Irvine, in 2000
Abstract:
Almost all software contains undiscovered bugs, ones that have not yet been exposed by testing or by users. Wouldn’t it be nice if there was a way to know the location of these bugs? This talk presents two approaches for predicting the location of bugs. The bug cache contains 10% of the files in a software project.
Duration : 0:56:19
28-May-2009 Google Wave Developer Preview
“Chapterized” 16 of 19
Duration : 0:3:58
Google Tech Talks
August 8, 2007
ABSTRACT
Advanced Topics in Programming Languages: JSR-305: Java annotations for software defect detection
This talk will describe the current status of JSR-305, Java annotations for software defect detection. This JSR will define several standard Java annotations for properties such as @Nonnegative and @Nonnull that can be used to document your design intentions in a way that be interpreted by multiple software tools (such as FindBugs and IntelliJ). In addition, the talk (and JSR) will discuss the need for inherited and default JSR-305 annotations and propose a way to provide them.
We’ll also discuss our proposal to define meta-annotations, that allow…
Duration : 1:3:2
Google TechTalks
July 6, 2006
William Pugh
ABSTRACT
I’ll talk about some of my experience in using and expanding static analysis tools for defect detection. The FindBugs tool developed at the Univ. of Maryland is now being widely used, including inside Google.
I’ll give an overview of FindBugs, show some of the kinds of errors we routinely find in production code, discuss the methodology we use for enhancing and expanding FindBugs and some of the recent additions to it, discuss ways of incorporating FindBugs into your development process (such as being able to get a report of all the warnings introduced since the last release of your software), and talk about the future of static analysis,…
Duration : 1:2:30
Google TechTalks
July 6, 2006
William Pugh
ABSTRACT
I’ll talk about some of my experience in using and expanding static analysis tools for defect detection. The FindBugs tool developed at the Univ. of Maryland is now being widely used, including inside Google.
I’ll give an overview of FindBugs, show some of the kinds of errors we routinely find in production code, discuss the methodology we use for enhancing and expanding FindBugs and some of the recent additions to it, discuss ways of incorporating FindBugs into your development process (such as being able to get a report of all the warnings introduced since the last release of your software), and talk about the future of static analysis,…
Duration : 1:2:31
Google TechTalks
March 8, 2006
Jim whitehead
Jim Whitehead is an Assistant Professor of Computer Science at the University of California, Santa Cruz. He has recently been developing a new degree program on computer gaming, the BS in Computer Game Engineering. Jim received his PhD in Information and Computer Science from UC Irvine, in 2000
Abstract:
Almost all software contains undiscovered bugs, ones that have not yet been exposed by testing or by users. Wouldn’t it be nice if there was a way to know the location of these bugs? This talk presents two approaches for predicting the location of bugs. The bug cache contains 10% of the files in a software project.
Duration : 0:56:20
Google Tech Talk
October 22, 2009
ABSTRACT
Automated Performance Test Data Collection and Reporting. Presented by David Burns and David Henderson, smartFOCUS DIGITAL, at the 4th Annual Google Test Automation Conference, October 21st, 22nd, 2009, Zurich, CH
Web applications are growing in size and complexity with every new release. The addition of slightly more JavaScript and HTML can lead to the site becoming sluggish without an obvious cause. Fortunately more organizations are taking note of the correlation between site speed and profitability. Without suitable tools, developers are left stabbing in the dark to resolve performance issues until the application feels faster. Luckily there are many tools available, such as YSlow, that can help you through the process of measuring the performance of your application. However gathering this data manually can be time consuming, laborious and prone to human inconsistencies. To illustrate the need for better performance information, we will outline the state of performance testing within the development cycle as carried out by many development teams around the world. We will then discuss the requirements for the system that has been created and implemented as a result of our research and development. The data gathering infrastructure, the tools used to create it and the scope of the data that is collected will be shown with solutions to problems encountered along the way. Performance statistics of a page, kept in a database, provide little useful information in isolation. When put into context with data from other pages and previous builds, the performance statistics suddenly become invaluable. To display this data in a digestible and comparable setting, a reporting portal will be demonstrated and its place within the development lifecycle explained. The final component of the system is the integration with the Tester’s Heads-Up Display (T.H.U.D.). This is a plugin that aids rapid diagnosis and reporting of bugs by overlaying performance data on a specific page, as well as providing access to source control and bug tracking systems. This presentation will show how ‘Automating Performance Test Data Collection and Reporting’ has improved the awareness of web performance issues within our company. It has provided the evidence required to instigate changes and measure their impact. An average 75% reduction in primed page size has been achieved as a direct result of the system’s introduction.
Bios: David Burns and David Henderson are both members of the development team at smartFOCUS DIGITAL, working on their SaaS solution.
David Burns is the Lead Test Engineer, working on the web accessible parts of the system. He is the test automation champion for smartFOCUS and heads up the Test Design Authority within the group trying to find best practices in testing of smartFOCUS applications. David is an active blogger at http://www.theautomatedtester.co.uk.
David Henderson graduated from the University of Southampton with a first class Masters in Engineering in 2007. He is a developer working on the front end development mainly dealing with JavaScript and C#. David is currently tinkering with the Android platform in his spare time, looking to write the next killer app.
Both have an unhealthy obsession with measuring and improving the speed and weight of the user experience.
Duration : 0:52:25
http://powerofcomparison.com/make-money-online-review-software.html
Know anything about software, like programming want to try yourself as custom application tester and get paid to find software bugs and errors? You can utilize platform as Utest for independent testers or can simply review software at SoftwareJudge. You can work for Google testing their beta software.
To see another free ways to make money online watch “80+ Free legitimate ways to make money online on Internet” here:
http://www.youtube.com/watch?v=GVVM25jWiek
Duration : 0:1:13
Google Tech Talks
September 12, 2008
ABSTRACT
While performance and power-efficiency are both important, correctness is perhaps even more important. In other words, if your software is misbehaving, it is little consolation that it is doing so quickly or power-efficiently. Google has already done a very impressive job of addressing one of the reasons why software may misbehave, which is that the underlying hardware may fail. In the Log-Based Architectures (LBA) project, however, we are focusing on perhaps an even more challenging source of misbehavior, which is that the application itself contains bugs, including obscure bugs that only cause problems during security attacks. Software bugs are difficult to recognize, and they are particularly problematic because they may cause every node in the system to fail (unlike hardware failures, which tend to be more isolated).
To help detect and fix software bugs, we have been exploring techniques for accelerating dynamic program monitoring tools, which we call “lifeguards”. Lifeguards are typically written today using dynamic binary instrumentation frameworks such as Valgrind or Pin . Due to the overheads of binary instrumentation, lifeguards that require instruction-grain information typically experience 30X-100X slowdowns, and hence it is only practical to use them during explicit debug cycles. Our goal is to reduce these overheads to the point where lifeguards can run continuously on deployed code. To accomplish this, we create a dynamic log of instruction-level events in the monitored application and stream this information to one or more lifeguards running on separate cores on the same chip multiprocessor (CMP).
In our results so far, we have shown that the basic logging approach typically reduces the slowdown by roughly an order of magnitude from roughly 30X to roughly 3X. In a recent ISCA paper, we demonstrated several hardware-based techniques that can eliminate redundancy in the even-driven lifeguards and reduce the slowdown to just 20%. In our ongoing research, we are attempting to achieve similar performance through software-only techniques (by extending dynamic compiler optimization techniques to eliminate redundancy within the lifeguards), and we are extending our support to parallel and concurrent environments. We believe that our techniques are applicable to any event-driven lifeguards that processes streams of events, and are compatible with sampling-based techniques that can further reduce the power and performance impacts of monitoring. This talk will describe the work that we have done so far, as well as our plans for future research.
Speaker: Todd Mowry
Todd C. Mowry is a Professor in the Computer Science Department at Carnegie Mellon University. He received his Ph.D. from Stanford University in 1994. He currently co-leads the Log-Based Architectures project and the Claytronics project. Prof. Mowry recently served as the Director of the Intel Research Pittsburgh lab, and he is currently on sabbatical at Stanford. He is an associate editor of ACM Transactions on Computer Systems.
Duration : 1:12:15
Posted in software bug | 
Tags: education, engedu, google, googletechtalks, talk, talks, techtalk, techtalks | 
3 Comments »