Patent application number | Description | Published |
20110247001 | Resource Management In Computing Scenarios - This patent application pertains to urgency-based resource management in computing scenarios. One implementation can identify processes competing for resources on a system. The implementation can evaluate an urgency of individual competing processes. The implementation can also objectively allocate the resources among the competing processes in a manner that reduces a total of the urgencies of the competing processes. | 10-06-2011 |
20110295844 | ENHANCING FRESHNESS OF SEARCH RESULTS - Methods, systems, and computer-storage media for improving the freshness, or the apparent freshness, of search results are described. In an embodiment, the first portion of search results presented on a search results page are based on responsiveness to the search query and a second portion of results describe only recently published documents that are responsive to the search query. In an embodiment, a more recent version of the document, which is not directly used to determine responsiveness, is used to build the caption for a search result. Another way to make search results appear fresh is to include a publication time within the search result caption. In one embodiment, the publication time is generated by calculating a point in time between when a document is first added to a search index and the previous time the search engine visited the site where the document was found. | 12-01-2011 |
20120047121 | CONTENT SIGNATURE NOTIFICATION - A client application installed on end user computers generates metadata from the content of web pages visited by end users and provides the metadata to a search engine. When an end user visits a web page, the end user's computer downloads and displays the web page to the end user. The client application may simultaneously access the web page content and generate this metadata in the form of a content signature of the web page from the web page content. The client application then provides the content signature to a search engine. The search engine may employ content signatures to identify new web pages to crawl and index. Additionally, the search engine may employ content signatures to identify changes to web pages and determine the crawl frequency of web pages. | 02-23-2012 |
20120127995 | BACKBONE NETWORK WITH POLICY DRIVEN ROUTING - A source device obtains a data packet that includes both a destination address and a payload. The source device selects an exit point address of multiple exit point addresses corresponding to the destination address based on one or more policies. The source device encapsulates the data packet with a header that includes the selected exit point address, and the encapsulated data packet is provided to the backbone network. The encapsulated data packet is routed through the backbone network based on the exit point address, and an edge router of the backbone network identifies an interface of the edge router that corresponds to the exit point address. The header is removed from the encapsulated data packet, and the data packet is added to a buffer of the interface for routing to one or more other devices outside of the backbone network. | 05-24-2012 |
20140195672 | AUTOMATED FAILURE HANDLING THROUGH ISOLATION - Embodiments are directed to isolating a cloud computing node using network- or some other type of isolation. In one scenario, a computer system determines that a cloud computing node is no longer responding to monitoring requests. The computer system isolates the determined cloud computing node to ensure that software programs running on the determined cloud computing node are no longer effectual (either the programs no longer produce outputs, or those outputs are not allowed to be transmitted). The computer system also notifies various entities that the determined cloud computing node has been isolated. The node may be isolated by powering the node down, by preventing the node from transmitting and/or receiving data, and by manually isolating the node. In some cases, isolating the node by preventing the node from transmitting and/or receiving data includes deactivating network switch ports used by the determined cloud computing node for data communication. | 07-10-2014 |
20140195853 | CLOUD MANAGEMENT USING A COMPONENT HEALTH MODEL - Embodiments are directed to establishing a model for testing cloud components and to preventing cascading failures in cloud components. In one scenario, a computer system models identified cloud components (including cloud hardware components and/or cloud software components) as health entities. Each health entity is configured to provide state information about the cloud component. The computer system establishes declarative safety conditions which declaratively describe cloud computing conditions that are to be maintained at the identified cloud components. The computer system then tests against the declarative safety conditions to determine which cloud components are or are becoming problematic. Upon determining that an error has occurred, the computer system notifies users of the error and the component at which the error occurred. Guarded interfaces are established to ensure that actions taken to fix the error do not cause further failures. | 07-10-2014 |
20140195861 | IMPLEMENTING RATE CONTROLS TO LIMIT TIMEOUT-BASED FAULTS - Embodiments are directed to implementing rate controls to limit faults detected by timeout and to learning and adjusting an optimal timeout value. In one scenario, a computer system identifies cloud components that have the potential to fail within a time frame that is specified by a timeout value. The computer system establishes a number of components that are allowed to fail during the time frame specified by the timeout value and further determines that the number of component failures within the time frame specified by the timeout value has exceeded the established number of components that are allowed to fail. In response, the computer system increases the timeout value by a specified amount of time to ensure that fewer than or equal to the established number of components fail within the time frame specified by the timeout value. | 07-10-2014 |
20140201564 | HEALING CLOUD SERVICES DURING UPGRADES - Embodiments described herein are directed to migrating affected services away from a faulted cloud node and to handling faults during an upgrade. In one scenario, a computer system determines that virtual machines running on a first cloud node are in a faulted state. The computer system determines which cloud resources on the first cloud node were allocated to the faulted virtual machine, allocates the determined cloud resources of the first cloud node to a second, different cloud node and re-instantiates the faulted virtual machine on the second, different cloud node using the allocated cloud resources. | 07-17-2014 |