Browse Prior Art Database

Time Zone Driven Workload Migration for Globalized Companies

IP.com Disclosure Number: IPCOM000138727D
Original Publication Date: 2006-Jul-31
Included in the Prior Art Database: 2006-Jul-31
Document File: 2 page(s) / 57K

Publishing Venue

IBM

Abstract

Proposed here is a mechanism for automatic migration of server images from one server farm to another.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Time Zone Driven Workload Migration for Globalized Companies

Many businesses today are global and have operational sites across the globe. Furthermore, these sites often have large computer server farms that serve local activities. Additionally, in most cases these server farms are connected to each other with broadband communication, which enables workloads that originate from one site to run on another site.

    The daily utilization profile of servers typically correlates to the human force workday. That is, utilization starts to rise somewhere between 8:00 and 9:00 AM (local time), peaks until late afternoon, and then slowly decreases. During the night, utilization drops to a minimum, and it starts rising again in the next morning. This utilization profile opens up an opportunity to utilize servers on the other side of the globe when it is night-time there. This is especially practical for computer jobs that need to run for days or weeks (e.g. data-bases, web servers, long computation jobs, etc.).

    Time zone information coupled with information on typical server utilization (at each time zone) can be used to optimize (in terms of total utilization) the automated process of migrating workloads.

    Proposed here is a mechanism for automatic migration of server images from one server farm to another. The mechanism will work as follows:

1. The mechanism builds on top of migration technologies such as:

a. Checkpoint/Restart, e.g., Encompass*
b. Virtual Server Migration, e.g., VMotion**
c. Process Migration, e.g. MOSIX***

Hence, the requirements of the underlying technology should be met to enable this mechanism. These requirements normally include shared storage between servers and compatible source and target server architectures.

2. Each server that participates in the mechanism is configured with a time zone and the times of low utilization.

3. Computer workloads destined to migrate on a time-zone based decision are run on as a migr...

Processing...
Loading...