The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jan. 19, 2010
Filed:
Aug. 05, 2003
Dale Koetke, Redmond, WA (US);
Xiaowen Shan, Kirkland, WA (US);
Nicole A. Bonilla, Redmond, WA (US);
Alec Dun, Redmond, WA (US);
Michael C. Price, San Diego, CA (US);
A. Perry Clarke, Bellevue, WA (US);
Marc R. Allen, Seattle, WA (US);
Joseph K. W. Chan, Redmond, WA (US);
Ronald E. Gray, Redmond, WA (US);
Aaron Hartwell, Duvall, WA (US);
Steven F. Goddard, Seattle, WA (US);
Dale Koetke, Redmond, WA (US);
Xiaowen Shan, Kirkland, WA (US);
Nicole A. Bonilla, Redmond, WA (US);
Alec Dun, Redmond, WA (US);
Michael C. Price, San Diego, CA (US);
A. Perry Clarke, Bellevue, WA (US);
Marc R. Allen, Seattle, WA (US);
Joseph K. W. Chan, Redmond, WA (US);
Ronald E. Gray, Redmond, WA (US);
Aaron Hartwell, Duvall, WA (US);
Steven F. Goddard, Seattle, WA (US);
Microsoft Corporation, Redmond, WA (US);
Abstract
The performance of client server interactions is measured by the interacting client. The client-generated performance data is efficiently transmitted to one or more servers by incorporating the performance data regarding one or more previous request/response cycles into a subsequent request. Performance data transmission is made more efficient by transmitting performance data context such as client, server and session details once per connection. Performance data is stored on the client until transmitted or until it has aged beyond a server specified maximum age. Performance data is aggregated on the server in memory resident accumulators. The server may have a set of accumulators for each server its clients communicate with as well as a set for each client. An accumulator value crossing a configurable threshold may trigger an event log entry. The number of performance data events in an event class may be limited to a maximum for a time period.