Patent Grant
9182922
1. Field
The subject matter disclosed herein relates to writing pacing and more particularly relates to dynamically adjusting write pacing.
2. Description of the Related Art
Data is typically written to and read from a storage system. Writes to the storage system may be paced to allow other operations to complete.
A method for dynamically adjusting write pacing is disclosed. A calculation module calculates an interval as a maximum threshold for a primary volume of a primary storage subsystem divided by a first maximum pacing level for a first importance level. Writes to the primary volume are stored as record sets in a cache and mirrored to a secondary volume of a secondary storage subsystem. The calculation module further calculates a first pacing level as a number of record sets that have not been mirrored to the secondary volume divided by the interval. The first pacing level is set to the first maximum pacing level if the first pacing level is greater than the first maximum pacing level. The calculation module also selects a first pacing delay associated with the first pacing level from a delay table. A pacing module delays writes for a first channel command word writing to the primary volume by the first pacing delay. At least a portion of the calculation module and pacing module include one or more of hardware and program code. The program code is stored on one or more computer readable storage media. An apparatus and computer program product also perform the functions of the method.
In order that the advantages of the embodiments of the invention will be readily understood, a more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive and/or mutually inclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.
Furthermore, the described features, advantages, and characteristics of the embodiments may be combined in any suitable manner. One skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments.
These features and advantages of the embodiments will become more fully apparent from the following description and appended claims, or may be learned by the practice of embodiments as set forth hereinafter. As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method, and/or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module,” or “system.”Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having program code embodied thereon.
Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in software for execution by various types of processors. An identified module of program code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of program code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. Where a module or portions of a module are implemented in software, the program code may be stored and/or propagated on in one or more computer readable medium(s).
The computer readable medium may be a tangible computer readable storage medium storing the program code. The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
More specific examples of the computer readable storage medium may include but are not limited to 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), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, a holographic storage medium, a micromechanical 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, and/or store program code for use by and/or in connection with an instruction execution system, apparatus, or device.
The computer readable medium may also be a computer readable signal medium. A computer readable signal medium may include a propagated data signal with 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, electrical, electro-magnetic, 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 program code 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 wire-line, optical fiber, Radio Frequency (RF), or the like, or any suitable combination of the foregoing
In one embodiment, the computer readable medium may comprise a combination of one or more computer readable storage mediums and one or more computer readable signal mediums. For example, program code may be both propagated as an electro-magnetic signal through a fiber optic cable for execution by a processor and stored on RAM storage device for execution by the processor.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++, PHP or the like and conventional procedural programming languages, such as the “C” programming language or similar 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).
The computer program product may be shared, simultaneously serving multiple customers in a flexible, automated fashion. The computer program product may be standardized, requiring little customization and scalable, providing capacity on demand in a pay-as-you-go model.
The computer program product may be stored on a shared file system accessible from one or more servers. The computer program product may be executed via transactions that contain data and server processing requests that use Central Processor Unit (CPU) units on the accessed server. CPU units may be units of time such as minutes, seconds, hours on the central processor of the server. Additionally the accessed server may make requests of other servers that require CPU units. CPU units are an example that represents but one measurement of use. Other measurements of use include but are not limited to network bandwidth, memory usage, storage usage, packet transfers, complete transactions etc.
When multiple customers use the same computer program product via shared execution, transactions are differentiated by the parameters included in the transactions that identify the unique customer and the type of service for that customer. All of the CPU units and other measurements of use that are used for the services for each customer are recorded. When the number of transactions to any one server reaches a number that begins to affect the performance of that server, other servers are accessed to increase the capacity and to share the workload. Likewise when other measurements of use such as network bandwidth, memory usage, storage usage, etc. approach a capacity so as to affect performance, additional network bandwidth, memory usage, storage etc. are added to share the workload.
The measurements of use used for each service and customer are sent to a collecting server that sums the measurements of use for each customer for each service that was processed anywhere in the network of servers that provide the shared execution of the computer program product. The summed measurements of use units are periodically multiplied by unit costs and the resulting total computer program product service costs are alternatively sent to the customer and or indicated on a web site accessed by the customer which then remits payment to the service provider.
In one embodiment, the service provider requests payment directly from a customer account at a banking or financial institution. In another embodiment, if the service provider is also a customer of the customer that uses the computer program product, the payment owed to the service provider is reconciled to the payment owed by the service provider to minimize the transfer of payments.
The computer program product may be integrated into a client, server and network environment by providing for the computer program product to coexist with applications, operating systems and network operating systems software and then installing the computer program product on the clients and servers in the environment where the computer program product will function.
In one embodiment software is identified on the clients and servers including the network operating system where the computer program product will be deployed that are required by the computer program product or that work in conjunction with the computer program product. This includes the network operating system that is software that enhances a basic operating system by adding networking features.
In one embodiment, software applications and version numbers are identified and compared to the list of software applications and version numbers that have been tested to work with the computer program product. Those software applications that are missing or that do not match the correct version will be upgraded with the correct version numbers. Program instructions that pass parameters from the computer program product to the software applications will be checked to ensure the parameter lists match the parameter lists required by the computer program product. Conversely parameters passed by the software applications to the computer program product will be checked to ensure the parameters match the parameters required by the computer program product. The client and server operating systems including the network operating systems will be identified and compared to the list of operating systems, version numbers and network software that have been tested to work with the computer program product. Those operating systems, version numbers and network software that do not match the list of tested operating systems and version numbers will be upgraded on the clients and servers to the required level.
In response to determining that the software where the computer program product is to be deployed, is at the correct version level that has been tested to work with the computer program product, the integration is completed by installing the computer program product on the clients and servers.
Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.
Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of the invention. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by program code. The program code may be provided to a processor of a general purpose computer, special purpose computer, sequencer, 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 data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
The program code may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
The program code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the program code which executed 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 schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of the program code 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. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and program code.
The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
The controller 130 may be a primary controller. The controller 130 may read data from the primary storage subsystem 110. In addition, the controller 130 may write data to the primary storage subsystem 110. In one embodiment, a host (not shown) writes data through the controller 130 to one or more primary volumes 105 using a channel command word (CCW). The controller 130 may be in communication with the server farm, a network, a data center, and the like. The primary volumes 105 may be managed by a Z/OS® operating system manufactured by International Business Machines Corporation (IBM) of Armonk, N.Y. The Z/OS® operating system may be the Z/OS® operating system as of the filing date of the present application.
To protect the data stored on the primary storage subsystem 110 from loss, the data mover 115 may mirror the data to the secondary storage subsystem 120. The data mover 115 may be a Z/OS® GLOBAL MIRROR™ manufactured by IBM. The Z/OS® GLOBAL MIRROR™ may be the Z/OS® GLOBAL MIRROR™ as of the filing data of the present application. The data mover 115 maintains a consistent copy of the data on the secondary storage subsystem 120. A unit of data that is mirrored is referred to herein as a record set. One of skill in the art will recognize that other designations for a unit of data are equivalent to a record set. The data mover 115 may store a record set that is to be mirrored to the secondary storage subsystem 120 in the cache 135 until the record set can be written or mirrored to the secondary storage subsystem 120.
The data mover 115 mirrors the record sets concurrently with read and write operations by the controller 130 to the primary storage subsystem 110. In order for a consistent copy of the primary storage subsystem data to be maintained on the secondary storage subsystem 120, writes to the primary storage subsystem 110 may be delayed so that the data mover 115 does not fall behind in mirroring the primary storage subsystem data. Delaying writes is referred to herein as write pacing.
Unfortunately, finding the appropriate level of write pacing is difficult. If the delays in writing data to the primary storage subsystem 110 are too long, the performance of the primary storage subsystem 110 is significantly degraded. However, if the delays in writing data to the primary storage subsystem 110 are too short, the data mover 115 may be unable to maintain a consistent copy of the primary storage subsystem data on the secondary storage subsystem 120. The embodiments described herein dynamically adjust write pacing so that a consistent copy of the primary storage subsystem data may be maintained on the secondary storage subsystem 120 while minimizing the impact on the performance of the primary storage subsystem 110.
In one embodiment, a pacing delay 210 pauses writes 215 after a specified number of CCW operations. In an alternate embodiment, the pacing delay 210 pauses writes after a specified time interval of CCW operations.
The pacing module 320 and the calculation module 325 may each comprise a computer readable storage medium such as the memory 310 storing program code. The program code may be executable by the processor 305 to perform the functions of the embodiments described herein.
The calculation module 325 may calculate an interval INT using equation 1 where T is a maximum threshold for a primary volume 105 of the primary storage subsystem 110 and MP1 is a first maximum pacing level for a first importance level I1.
INT=T/(MP1) Equation 1
In one embodiment, if the maximum pacing level is zero, the volume pacing level for the primary volume 105 is used. If the volume pacing level for the primary volume 105 is zero, a pacing level of zero is employed. The first maximum pacing level MP1 may be retrieved from the importance table 330 for a specified first importance level I1. Table 1 is exemplary of the importance table 330 associating maximum pacing levels MP with importance levels I, but is not limiting. One of skill in the art will recognize that the embodiments may be practiced with an importance table 330 with other values.
In one embodiment, an importance level I is associated with each primary volume 105. The calculation module 325 further calculates a first pacing level PL1 using Equation 2, wherein SF is a number of record sets 205 that have not been mirrored to a secondary volume 125 and INT is the interval.
PL1=SF/INT Equation 2
In one embodiment, the first pacing level PL1 is set to the first maximum pacing level MP1 if the first pacing level PL1 is greater than the first maximum pacing level MP1. The calculation module 325 further selects the first pacing delay 210 associated with the first pacing level PL1 from a delay table 335 that associates pacing levels PL with pacing delays 210. Table 2 illustrates one embodiment of the delay table 335. One of skill in the art will recognize that the embodiments may be practiced with other delay table values.
The pacing delays 210 may be specified in milliseconds. Alternatively, the pacing delays 210 may be specified in microseconds, clock cycles, and the like. The pacing module 320 may delay writes 215 for an operation such as a CCW operation writing to a primary volume 105 by the first pacing delay 210. As a result, writes 215 are delayed by the pacing delay 210.
The method starts, and in one embodiment the calculation module 325 associates 505 a maximum pacing level MP with each importance level I in the importance table 330. In one embodiment, the calculation module 325 employs a Set Session Characteristics (Defined Subsystem Operation) DSO to associate 505 a maximum pacing value MP with each importance level I. In one embodiment, a user may establish the maximum pacing value for each importance level. The data mover 115 may communicate the maximum pacing values and importance levels to the controller 130 via the Set Session Characteristics DSO. The calculation module 325 embodied in the controller 130 may calculate the importance level.
In one embodiment, an importance level I is calculated from a service level assigned to a workload. For example, a first workload may be assigned a service level of 1. The importance level may be calculated as 1 from the service level. Each primary volume 105 may have an importance level I. The importance level I and the maximum pacing levels MP may be defined by the administrator in PARMLIB and communicated to the calculation module 325 using an establish command for the data mover 115.
The calculation module 325 may further associate 507 a maximum threshold to each primary volume 105 and the method 500 ends. In one embodiment, the maximum threshold is specified by the administrator.
The method 501 starts, and in one embodiment, the calculation module 325 associates 510 a pacing delay 210 with each pacing level PL in the delay table 335. In one embodiment, the pacing delay 210 is associated 510 with the pacing level PL using an initialization command.
The method 502 starts, and in one embodiment the calculation module 325 calculates 515 the interval INT using equation 1 where T is a maximum threshold for a primary volume 105 of the primary storage subsystem 110 and MP1 is a first maximum pacing level for a first importance level I1. The first maximum pacing level MP1 may be retrieved from an importance table 330 for a specified first importance level I1 of the primary volume 105 to which a write is directed.
The calculation module 325 further calculates 520 a first pacing level PL1 using Equation 2, wherein SF is a number of record sets 205 that have not been mirrored to a secondary volume 125 and INT is the interval. The first pacing level PL1 is set to the first maximum pacing level MP1 if the first pacing level PL1 is greater than the first maximum pacing level MP1.
The calculation module 325 further selects 525 the first pacing delay 210 associated with the first pacing level PL1 from the delay table 335 that associates pacing levels PL with pacing delays 210. The pacing module 320 may delay 530 writes for one or more CCW operations writing to a primary volume 105 by the first pacing delay 210 and the method 502 ends. As a result, writes 215 are delayed by the pacing delay 210.
By selecting a pacing delay 210 based on the calculations of the interval and the pacing level, the embodiments dynamically modify writing pacing so that a consistent copy of the primary storage subsystem data is maintained on the secondary storage subsystem 120 while minimizing performance degradation to the primary storage subsystem 110.
The embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5623599 | Shomler | Apr 1997 | A |
| 5926834 | Carlson et al. | Jul 1999 | A |
| 5991835 | Mashimo et al. | Nov 1999 | A |
| 6687766 | Casper et al. | Feb 2004 | B1 |
| 7523271 | Houzenga et al. | Apr 2009 | B2 |
| 7546434 | McClure et al. | Jun 2009 | B2 |
| 7702871 | Arnon et al. | Apr 2010 | B1 |
| 8032581 | Hathorn et al. | Oct 2011 | B2 |
| 20070185936 | Derk et al. | Aug 2007 | A1 |
| 20090019443 | Jakob | Jan 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| 2060973 | May 2009 | EP |
| Number | Date | Country | |
|---|---|---|---|
| 20150074363 A1 | Mar 2015 | US |
