Worldwide access to the World Wide Web has led to organizations and businesses using web sites as a way to provide information to customers. With faster network speeds to access web sites and increased content on the Web, the performance and speed of operation and navigation of web sites may be important to web site owners. Network providers wish to quantify the performance of web sites and improve the operation and trouble shooting of web sites. While performance management software may be used to collect diagnostic data on web site performance, an administrator or other engineering staff may lack tools for analyzing the diagnostic information and identifying the source of performance problems or mitigate the effects of performance problems.
Various embodiments of the present invention are directed to a method including performing operations as follows on a processor. The operations include receiving a user selection of a content item on a web page in a web browser executing on a device, obtaining resource timing information corresponding to network timing information associated with a web resource associated with the content item, determining a callback execution time associated with the web resource, aggregating performance information including the resource timing information and the callback execution time associated with the web resource, and communicating, to a device associated with the network operator, the performance information including the resource timing information and the callback execution time associated with the web resource.
In some embodiments, operations performed on the processor may include sending a request to obtain the web resource associated with the content item, responsive to the receiving the user selection, and performing a callback operation, responsive to completion of the sending the request. A resource table may be processed by performing operations including the resource timing information, responsive to a completion of the performing the callback operation. Sending the request to obtain the web resource may include determining a system request send operation associated with the web resource, responsive to the receiving the user selection, and executing a send wrapper operation that redefines the system request send operation, responsive to the determining the system request operation. Operations may include determining a request start time associated with the web resource, responsive to the executing the send wrapper operation, and setting a harvest ready flag to an indication of not being ready to harvest a resource table including the resource timing information.
In some embodiments, performing the callback operation may include executing a callback wrapper operation that redefines the callback operation, and determining a callback execution time associated with the web resource. Determining the callback execution time associated with the web resource may include determining a callback execution start time, executing the callback operation, and determining a callback execution end time. The callback execution time may include the callback execution start time and the callback execution end time.
In some embodiments, operations may include setting a harvest ready flag to an indication of being ready to harvest the resource table including the resource timing information, responsive to the performing the callback operation. A resource table including the resource timing information may be processed, responsive to the harvest ready flag indicating being ready to harvest the resource table. Processing the resource table including the resource timing information may include generating a binary sorted proprietary resource list based on a plurality of web resources in the resource table, and determining the resource timing information associated with the web resource, wherein determining the resource timing information associated with the web resource including processing elements of the binary sorted proprietary resource list.
In some embodiments, determining the callback execution time associated with the web resource may include correlating the callback execution time associated with the web resource with an element of the binary sorted proprietary resource list, and associating the callback execution time with the resource timing information of the web resource based on the correlating the callback execution time. Correlating the callback execution time associated with the web resource with the element of the binary sorted proprietary resource list may include identifying an element of the binary sorted proprietary resource list. Identifying the element of the binary sorted proprietary resource list may include performing a binary search of the binary sorted proprietary resource list.
In some embodiments, correlating the callback execution time associated with the web resource with the element of the binary sorted proprietary resource list may further include determining an index of the element of the binary sorted proprietary resource list that was identified, and identifying the callback execution time associated with the web resource, based on the index of the element of the binary sorted proprietary resource list.
Various embodiments of the present inventive concept include an electronic device, including a processor, and a memory coupled to the processor and including computer readable program code embodied in the memory that when executed by the processor causes the processor to perform operations as follows on a processor. The operations include receiving a user selection of a content item on a web page in a web browser executing on a device, obtaining resource timing information corresponding to network timing information associated with a web resource associated with the content item, determining a callback execution time associated with the web resource, aggregating performance information including the resource timing information and the callback execution time associated with the web resource, and communicating, to a network operator, the performance information including the resource timing information and the callback execution time associated with the web resource.
In some embodiments, the processor of the electronic device may be further configured to perform operations including sending a request to obtain the web resource associated with the content item, responsive to the receiving the user selection, performing a callback operation, responsive to completion of the sending the request, and processing a resource table including the resource timing information, responsive to a completion of the performing the callback operation. The processor may be further configured to perform operations including determining a system request send operation associated with the web resource, responsive to the receiving the user selection, executing a send wrapper operation that redefines the system request send operation, responsive to the determining the system request operation, setting a harvest ready flag to an indication of not being ready to harvest a resource table including the resource timing information, executing a callback wrapper operation that redefines the callback operation, and determining a callback execution time associated with the web resource. The callback execution time may include the callback execution start time and the callback execution end time.
In some embodiments, the processor of the electronic device may be further configured to perform operations including setting a harvest ready flag to an indication of being ready to harvest the resource table including the resource timing information, responsive to the performing the callback operation, generating a binary sorted proprietary resource list based on a plurality of web resources in a resource table, responsive to the harvest ready flag indicating being ready to harvest the resource table, and determining the resource timing information associated with the web resource, wherein determining the resource timing information associated with the web resource includes processing elements of the binary sorted proprietary resource list.
In some embodiments, the processor of the electronic device may be further configured to perform operations including correlating the callback execution time associated with the web resource with an element of the binary sorted proprietary resource list, identifying an element of the binary sorted proprietary resource list, wherein the identifying the element of the binary sorted proprietary resource list includes performing a binary search of the binary sorted proprietary resource list, associating the callback execution time with the resource timing information of the web resource based on the correlating the callback execution time, determining an index of the element of the binary sorted proprietary resource list that was identified, and identifying the callback execution time associated with the web resource, based on the index of the element of the binary sorted proprietary resource list.
Various embodiments of the present inventive concept include a computer program product, that includes a non-transitory computer readable storage medium storing computer readable program code which when executed by a processor of an electronic device causes the processor to perform operations as follows on a processor. The operations include receiving a user selection of a content item on a web page in a web browser executing on a device, obtaining resource timing information corresponding to network timing information associated with a web resource associated with the content item, determining a callback execution time associated with the web resource, aggregating performance information including the resource timing information and the callback execution time associated with the web resource, and communicating, to a network operator, the performance information including the resource timing information and the callback execution time associated with the web resource.
It is noted that aspects described with respect to one embodiment may be incorporated in different embodiments although not specifically described relative thereto. That is, all embodiments and/or features of any embodiments can be combined in any way and/or combination. Moreover, other methods, systems, articles of manufacture, and/or computer program products according to embodiments of the inventive subject matter will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems, methods, articles of manufacture, and/or computer program products be included within this description, be within the scope of the present inventive subject matter, and be protected by the accompanying claims. It is further intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.
Features of embodiments will be more readily understood from the following detailed description of specific embodiments thereof when read in conjunction with the accompanying drawings, in which:
In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In some instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present disclosure. It is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination. Aspects described with respect to one embodiment may be incorporated in different embodiments although not specifically described relative thereto. That is, all embodiments and/or features of any embodiments can be combined in any way and/or combination.
Businesses, applications, organizations, and/or groups use web pages as an interface to users. Ubiquitous availability of computers and/or mobile devices provide access to most persons worldwide to a web browser capable of connecting to the internet and accessing websites associated with businesses, applications, organizations, and/or groups. Websites may include numerous web pages that each provide different information to users. Some websites may have a separate web page for each use case, such as a home page (home.html), products page (products.html), about page (about.html), etc. As a user navigates a web page, user selections may trigger one or more resources to be transferred to the browser. However, if a significant amount of time is needed to obtain or download these resources, the user may see a busy signal, such as an hour glass on the user interface or display. Long wait times are generally unacceptable to users and diminish the user experience on a web page. Therefore, network operators may desire to have information regarding performance of webpages and specific information about individual resources.
Resources within a web page can be classified as two major types: static or dynamic. Static resources may include items that are downloaded automatically through HTML tags such as <script>, <img>, <css> etc. Dynamic resources may be variable content, which is either uploaded or downloaded in a web request, such as an Asynchronous JavaScript And XML (AJAX) request. For example, AJAX in JavaScript may use an XMLHttpRequest (or helper frameworks such as j Query) to enable the browser/client to send/receive content from a remote web server. However, many types of content may be obtained through this framework, and thus XML is discussed herein as a non-limiting example. Additionally, in some embodiments, web requests, such as AJAX requests, may support a synchronous calling mode, although it may not be preferred in some applications since the synchronous call mode may block the user experience. Thus, the non-limiting examples described herein will be in the context of asynchronous web/AJAX requests. In either the synchronous or asynchronous cases, the framework response, which may take notable time to process on the client/browser, may be processed in a variety of user implemented function callbacks such as onload, onloadend and readystatechange. Some embodiments described herein are described with reference to a function. A function may be software that runs on a processor. A function may be used to refer to methods in a web environment or an object-oriented environment, in some embodiments. Providing the timing measurements on these functions is something a tool such as the CA Technologies Browser Agent may do to provide metrics such as the Callback Execution Time (CBET). However, the CBET may not be as useful by itself but may be more valuable when used in conjunction with other performance information for the resources.
Timing metrics may be obtained for many resources through the Performance Resource Timing (PRT) API provided by JavaScript/Browser. Specifically, these timing metrics may provide timing visibility into aspects of the network call for a given resource, such as domain lookup start/end, connection start/end, etc. CBET for a resource may not be provided by the performance resource timing API, but may be obtained via proprietary instrumentation, as described herein. Being able to correlate CBET with other timing metrics from PRT may provide a superior and more complete start-to-end call life-cycle on the true timing cost of a web resource. From request to response to client side processing, the CBET may provide an end-to-end view that may be important to understand the performance of a web page.
When a web page is performing AJAX related functionality, often times a busy spinner may appear, indicating that a portion of the page is undergoing an asynchronous update. Web page users are often free to click elsewhere on the page during this asynchronous update. However, if a user is waiting for a significant amount of time on the portion of the page, then the user experience may be suboptimal. For example, if a user is on a news website, the user may click a “more” content item on the web page to obtain more news stories. However, this updating of more news stories may take a long time, from the user's point of view. It may be desired by a network operator and/or a network provider to understand the source of the problem such a problem in the network, or a problem in the client side processing. Many different metrics considered together may provide a higher level of resource visibility. It may be desired to provide CBET metrics for AJAX resources. In other words, the CBET cost may be desired along with the PRT metrics for individual web resources to identify bottleneck related to the webpage.
Determining correlation between the CBET and the PRT metrics for individual web resources may not easy in many cases. A first challenge may be that the web browser/PRT API may not notify when a new resource has completed. For example, completed AJAX resources may be added to the web browser's PRT table (i.e. resource table), but there may not be a way in a web script such as JavaScript to register a callback on the resource table. Thus the resource table may need to be checked periodically to look for new updates. Since an instrumentation tool may not know when a web resource will complete, proprietary resource instrumentation for CBET may be needed to reconcile the CBET time against resource table entries. The ordering of reconciliation may be important.
Once a CBET has been determined, the resource table may be searched. However, the resource table may not yet contain an entry during CBET determination. Another challenge is that a resource could have the same name, which would look identical in the table. This may be solved by using the name and resource start time compared with the name and start time obtained from tool's proprietary instrumentation. However, this solution could pose an issue since JavaScript's Date function could be offset by several milliseconds compared to the entry in resource table. Therefore, the start time of the resource must be within an acceptable threshold. Another challenge may be that the duration value on the PRT object may be computed by the web browser tool by using a difference responseEnd—startTime. However, if the browser tool adds the CBET, which essentially occurs in a final phase, then the total duration may need to be updated again. Duration may be a difference between the callback execution end time and the callback execution start time, (e.g. callbackExecutionTime End—callbackExecutionTime startTime). Thus total duration for the resource will then be callbackExecutionTime End—startTime. Details of obtaining the CBET will now be described with respect to the accompanying figures.
Referring now to
Referring now to
Still referring to
Referring now to
Still referring to
Still referring to
Referring now to
Referring now to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
The processor 2030 may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor) that may be collocated or distributed across one or more networks. The processor 2030 is configured to execute computer program code 2012 in the memory 2010, described as a non-transitory computer readable medium, to perform at least some of the operations described herein as being performed by an electronic device. The computer program code 2012 when executed by the processor 2030 causes the processor 2030 to perform operations in accordance with one or more embodiments disclosed herein for the electronic device 2000. The electronic device 2000 may further include a user input interface 2020 (e.g., touch screen, keyboard, keypad, mouse, etc.) and/or a display device 2022.
In the above-description of various embodiments of the present disclosure, aspects of the present disclosure may be illustrated and described herein in any of a number of patentable classes or contexts including any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Accordingly, aspects of the present disclosure may be implemented entirely hardware, entirely software (including firmware, resident software, micro-code, etc.) or combining software and hardware implementation that may all generally be referred to herein as a “circuit,” “module,” “component,” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product comprising one or more computer readable media having computer readable program code embodied thereon.
Any combination of one or more computer readable media may be used. The computer readable media may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an appropriate optical fiber with a repeater, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, JavaScript, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python or the like, conventional procedural programming languages, such as the “C” programming language, Visual Basic, Fortran 2003, Perl, COBOL 2002, PHP, ABAP, LabVIEW, dynamic programming languages, such as Python, Ruby and Groovy, or other programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) or in a cloud computing environment or offered as a service such as a Software as a Service (SaaS).
Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable instruction execution apparatus, create a mechanism for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that when executed can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions, when stored in the computer readable medium, produce an article of manufacture including instructions which when executed, cause a computer to implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable instruction execution apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatuses or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various aspects of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular aspects only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. Like reference numbers signify like elements throughout the description of the figures.
It will be understood that, although the terms “first,” “second,” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. Thus, a first element could be termed a second element without departing from the teachings of the inventive subject matter.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this inventive concept belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and this specification and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The aspects of the disclosure herein were chosen and described to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure with various modifications as are suited to the particular use contemplated.