This application is based upon and claims the benefit of priority of the prior Japanese Patent Application No. 2014-083060, filed on Apr. 14, 2014, the entire contents of which are incorporated herein by reference.
The embodiments discussed herein are related to apparatus and method for allocating data processing between transfer source and destination devices.
In the past, data which is stored in a first information processing device, has been transferred to a second information processing device. In the second information processing device, data conversion is executed with respect to the transferred data, and data storage is performed by a format which is different from the first information processing device.
Japanese Laid-open Patent Publication No. 2007-86883 is an example of the related art.
According to an aspect of the invention, in a case of executing, on transfer data which is to be transferred from a first information processing device to a second information processing device, data processing that complies with a data storage format in the second information processing device, an apparatus determines, as a target information processing device for executing the data processing, one of the first and second information processing devices, based on information on the data processing which includes a variation characteristic of data amount before and after the data processing.
The object and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, as claimed.
When an amount of data which is transferred between the information processing devices increases, time required for the data transfer may also increase. In order to suppress increase in time to be used for the data transfer, and improve efficiency of the data transfer, it is desirable to decrease the amount of data to be transferred. By performing data processing, such as data conversion, on data, the amount of the data may be changed, and, for example, the amount of the data at the time of the transfer may be reduced.
In the related art, the data conversion is equally performed by a second information processing device to which the data is transferred, and thus, the data amount at the time of the transfer may not be reduced, and the efficiency improvement of the data transfer may not be achieved.
First, problems in data transfer which is accompanied with data processing between information processing devices, will be described before describing details of each embodiment.
For example, in a case of performing the data transfer which is accompanied with the data conversion between a plurality of servers, it is assumed that a dedicated data conversion server is arranged, which intensively executes the data conversion at the time of the data transfer between the servers.
In this case, the data is transferred to a transfer destination server from a transfer source server by way of the data conversion server. Therefore, when an amount of transferred data is small, a large problem does not occur, but when the amount of transferred data is large, the transfer time increases by going through an extra transfer path. Additionally, in order to convert the data, a disk area for temporarily storing the data has to be arranged in the data conversion server. However, when the amount of transferred data is large, the disk area has to be acquired in a large size, and a cost of hardware resources also increases.
Moreover, as the related art described above, in a case of equally performing the data conversion by the transfer destination server, it is not possible to improve efficiency of the data transfer in consideration of the data conversion. For example, when contents of the data conversion is specified by the transfer source server, and the data amount decreases by the data conversion, efficiency improvement of the data transfer is achieved in a case that the data is transferred to the transfer destination server after performing the data conversion by the transfer source server.
However, data conversion in data transfer may have a plurality of types, and variation in amount of data before and after conversion of the data is changed according to a type of the data conversion. For example, when the data conversion is compression processing of the data, since the data amount decreases after the data conversion, efficiency in data transfer becomes better when data is transferred to a transfer destination server after performing the data conversion by a transfer source server. Moreover, when the data conversion is the processing of converting the data of a comma-separated values (CSV) format into the data of an extensible markup language (XML) format, data amount increases after the data conversion. Therefore, efficiency in data transfer becomes better when data conversion is performed by a transfer destination server after the data is transferred to the transfer destination server. In this manner, since a mode of improving the efficiency of data transfer is changed according to a type of data conversion, it is difficult to categorically determine one of the transfer source server and the transfer destination server as a server which executes the data conversion.
Additionally, when the data conversion is performed by the transfer source server, it is necessary for the transfer source server to specify a format in which the transferred data is stored in the transfer destination server.
In consideration of the problems described above, in the embodiment, a server which executes the data conversion is properly determined, depending on the contents of the data conversion to be executed.
Hereinafter, examples of the embodiments according to technologies discussed herein, will be described in detail, with reference to the drawings.
As illustrated in
As illustrated in
The data conversion application information management unit 11 manages an application (referred to as “data conversion application”, hereinafter) for executing the data conversion which is accompanied with the data transfer between the storage servers 30, and meta information which is accompanied with the data conversion application. The meta information includes a name of the data conversion application, and a characteristic of the data conversion application.
The characteristic of the data conversion application is a characteristic indicating variation in data amount before and after the data conversion executed by the data conversion application. In the first embodiment, as a characteristic of the data conversion application, a Before characteristic, an After characteristic, and an Any characteristic are used.
The Before characteristic is a characteristic representing that the efficiency becomes better when the transfer source server S performs the data conversion, such as a case where the data amount decreases after the data conversion. For example, the characteristic of the data conversion application which executes the compression processing, is the Before characteristic.
The After characteristic is a characteristic representing that the efficiency becomes better when the transfer destination server R performs the data conversion, such as a case where the data amount increases after the data conversion. For example, the characteristic of the data conversion application which executes a conversion from the data of the CSV format to the data of the XML format, is the After characteristic.
The Any characteristic is a characteristic representing that the efficiency does not change largely regardless whether any one of the transfer source server S and the transfer destination server R performs the data conversion, such as a case where variation in data amount is small after the data conversion or the variation is undefined. For example, the characteristic of the data conversion application that executes processing of converting commas to colons in stream conversion for which reading of the whole data is unnecessary, is the Any characteristic.
The data conversion application information management unit 11 accepts a data conversion application (program) which is registered by an operation of a user, and the meta information which is accompanied with the data conversion application, and stores the data conversion application in a predetermined storage area. Additionally, the data conversion application information management unit 11 stores the accepted meta information in a data conversion application information table 21 which is stored in the management DB 20.
Moreover, the statistical information management unit 12 obtains and manages the statistical information which is obtained by executing the data conversion application on each storage server 30. In the first embodiment, a data throughput per unit time for each data conversion application, and a variation rate of the data amount after the data conversion for each data conversion application, are used as statistical information.
The data throughput per unit time is statistical information that is used for considering, at the time of determining the storage server 30 which executes the data conversion, a characteristic indicating, for example, that the data conversion tends to take a long time even when the data throughput is small.
A variation rate of the data amount after the data conversion is statistical information that is used for considering, at the time of determining the storage server 30 which executes the data conversion, statistical data regarding the variation of data after the data conversion, which is unable to be specified by the characteristic of the data conversion application. Since a change in the variation of the data amount after the data conversion may occur due to the difference of target data even when the data conversion of the same type is performed, the variation rate of the data amount after the data conversion is used as a value in which an actual result value is reflected.
The statistical information management unit 12 obtains, from an execution instruction (will be described later in detail) of the data transfer which is accepted by the determination unit 14, the data conversion to be executed, the transfer source server S, and the information of transfer target data, and obtains, from the transfer source server S, the data amount of the transfer target data. When information on the data amount of the transfer target data is also included in the execution instruction, the information may be used. For example, the statistical information management unit 12 adds an entry of the data conversion application which is subjected to the execution instruction, to a data conversion application actual result table 22 as illustrated in
When the storage server 30 which executes the data conversion application is determined by the determination unit 14 (will be described later in detail), the statistical information management unit 12 stores the name of the determined storage server 30 in the item of the storage name of the data conversion application actual result table 22. In addition, when the execution of the data conversion application is started by the storage server 30, the statistical information management unit 12 sets the execution status flag at true. Along therewith, every time the data conversion application is executed, the statistical information management unit 12 obtains the start time of the data conversion, the finish time, and the data amount after the conversion, and stores the obtained values in the items corresponding thereto. When the execution of the data conversion application is finished, the statistical information management unit 12 sets the execution status flag at false. When the contents of the entry are reflected in the statistical information which is stored in the data conversion application information table 21, the statistical information management unit 12 deletes the entry corresponding thereto.
Moreover, when the execution of the data conversion application is finished, the statistical information management unit 12 calculates execution time of each execution of the data conversion application from the difference between the start time and the finish time, with reference to the data conversion application actual result table 22. The statistical information management unit 12 adds up each of the calculated execution time and the data amount before the conversion corresponding thereto, to each of the execution time of the data conversion application which is executed in the past and the data amount before the conversion corresponding thereto. The statistical information management unit 12 calculates the data throughput per unit time for each data conversion application, based on the data amounts before the conversion which are added together/the execution time which is added together. Furthermore, the statistical information management unit 12 may calculate the data throughput per unit time for each execution of the data conversion application, and from an average of the calculated data throughput per unit time which have been calculated in the past, the statistical information management unit 12 may calculate the data throughput per unit time for each data conversion application.
Moreover, the statistical information management unit 12 obtains the variation rate of the data amount after the data conversion by calculating a formula of “(the data amount after the conversion−the data amount before the conversion)/the data amount before the conversion”, for each execution of the data conversion application, with reference to the data conversion application actual result table 22. The statistical information management unit 12 creates probability distribution of the variation rates of the data amount after the data conversion which is calculated with respect to each execution of the data conversion application. Therefore, the statistical information management unit 12 determines the variation rate of the data amount after the data conversion which has the largest probability in a range of the average value±standard deviation in the probability distribution, as a data variation rate for each data conversion application. Furthermore, the statistical information management unit 12 may calculate the variation rate of the data amount after the data conversion for each data conversion application, based on other statistical amounts, such as the average of the variation rates of the data amounts after the data conversion which are calculated for each execution of the data conversion application.
For example, the statistical information management unit 12 stores the calculated data throughput per unit time for each data conversion application, and the data variation rate after the data conversion for each data conversion application, in the data conversion application information table 21 illustrated in
The load information management unit 13 obtains and manages load information of each storage server 30. In a state that the load of the storage server 30 is large, it is expected that the time taken in the data conversion processing will increase. Therefore, the load information of the storage server 30 together with the statistical information of the data conversion application, are used at the time of determining the storage server 30 which executes the data conversion. In the first embodiment, a concurrency number of data conversion applications, and a resource use situation are used as load information.
The concurrency number of data conversion applications is the number of data conversion applications which are executed at a certain point of time, by each storage server 30. The resource use situation is a use situation of the resource at a certain point of time, by each storage server 30. For example, the resource use situations include a use rate of a CPU, a use rate of a memory, an input-output rate of an external storage device (disk), a capacity of a swap area, a network transfer rate and the like.
The load information management unit 13 periodically obtains the concurrency number of data conversion applications, by counting the number of data conversion applications being executed for each storage server 30, with reference to the data conversion application actual result table 22 which is managed by the statistical information management unit 12. Moreover, the load information management unit 13 periodically obtains each resource use situation, from each storage server 30. Then, the load information management unit 13 stores the obtained load information, in a load information table 23 which is stored in the management DB 20.
The determination unit 14 accepts the execution instruction of the data transfer which is accompanied with the data conversion between the storage servers 30, from a user or other processes. An execution instruction of data transfer is configured to designate, at least, the transfer source server S, the transfer destination server R, the target data, and the type of the data conversion. The determination unit 14 determines the storage server 30 which executes the data conversion, from the transfer source server S and the transfer destination server R which are designated in the execution instruction of the data transfer, so as to improve the efficiency of the data transfer, based on the information which is stored in each table of the management DB 20. Hereinafter, the storage server 30 which executes the data conversion is referred to as “data conversion execution server”.
The instruction unit 15 reads out, from the predetermined storage area, the data conversion application for performing the data conversion which is designated in the execution instruction of the data transfer, and transmits the read data conversion application to the data conversion execution server which is determined by the determination unit 14. According to the execution instruction of the data transfer, the instruction unit 15 notifies the storage server 30 which becomes the transfer source server S, of information on the target data of the data transfer and the transfer destination server R, as instruction information. Moreover, the instruction unit 15 gives the instruction of the acceptance of the data which is transferred from the transfer source server S, to the storage server 30 which becomes the transfer destination server R. When the data conversion execution server is the transfer source server S, the instruction unit 15 instructs the transfer source server S to perform data conversion of the data which is stored in the data conversion execution server. On the other hand, when the data conversion execution server is the transfer destination server R, the instruction unit 15 instructs the transfer destination server R to perform data conversion of the data which has been transferred from the transfer source server S.
In this way, when the data conversion execution server is the transfer source server S, the data conversion by the transfer source server S, and the transfer of the data from the transfer source server S to the transfer destination server R, are executed. When the data conversion execution server is the transfer destination server R, the data transfer from the transfer source server S to the transfer destination server R, and the data conversion by the transfer destination server R, are executed.
Next, the storage server 30 will be described. Since the storage server 30A and the storage server 30B have the same configurations, here, the storage server 30A will be described. The storage server 30A includes a data conversion application execution base 31, a data conversion application execution unit 32, and a transfer unit 33.
The data conversion application execution base 31 provides a base (called “Runtime”) for executing the data conversion application. The data conversion application execution unit 32 executes the data conversion application which is transmitted from the instruction unit 15. The transfer unit 33 performs the transfer (Sender) of the data, or the acceptance (Receiver) of the data, according to the instruction from the instruction unit 15.
For example, the transfer control device 10 may be realized by a computer 40 illustrated in
The storage unit 46 may be realized by a hard disk drive (HDD), a solid state drive (SSD), a flash memory or the like. In the storage unit 46 as a storage medium, a transfer control program 50 causing the computer 40 to function as a transfer control device 10 is stored. Moreover, the storage unit 46 includes a management DB storage area 60.
The CPU 42 loads the transfer control program 50 that has been read out from the storage unit 46, into the memory 44, and sequentially executes processes which are included in the transfer control program 50. Additionally, the CPU 42 reads out information which is stored in the management DB storage area 60, and load the information as each table illustrated in
The transfer control program 50 includes a data conversion application information management process 51, a statistical information management process 52, a load information management process 53, a determination process 54, and an instruction process 55. The CPU 42 operates as a data conversion application information management unit 11 illustrated in
For example, the transfer control device 10 may be realized by a semiconductor integrated circuit, more specifically, by an application specific integrated circuit (ASIC) or the like.
Moreover, the storage server 30 may be realized by the computer including the CPU, the memory, the nonvolatile storage unit, the input-output I/F, and the network I/F.
Next, the operations of the transfer control device 10 according to the first embodiment will be described. Upon receiving the execution instruction of the data transfer which is accompanied with the data conversion between the storage servers 30, from the user or other processes, the transfer control device 10 executes the data conversion execution server determination processing (will be described later in detail) illustrated in
The statistical information management unit 12 adds an entry to the data conversion application actual result table 22, based on the information obtained from the execution instruction of the data transfer, and manages the actual result data which is obtained by executing the data conversion application. Moreover, the statistical information management unit 12 obtains the statistical information of each data conversion application, with reference to the data conversion application actual result table 22, and manages the obtained statistical information by storing the same in the data conversion application information table 21.
Additionally, the load information management unit 13 periodically obtains the load information from the storage server 30 while each storage server 30 operates, and manages the obtained load information by storing the same in the load information table 23.
Moreover, when the data conversion application and the meta information are registered by a user, the data conversion application information management unit 11 accepts the data conversion application and the meta information. The data conversion application information management unit 11 manages the data conversion application and the meta information by storing the accepted data conversion application in the predetermined storage area, and by storing the meta information in the data conversion application information table 21.
Here, the data conversion execution server determination processing which is executed by the transfer control device 10, will be described with reference to
First, in step S11 of
Next, in step S12, the determination unit 14 determines whether the characteristic of the data conversion application is the Any characteristic. In the case of the Any characteristic, the processing shifts to step S13, and in the case of the Before characteristic or the After characteristic, the processing shifts to step S17.
In step S13, the determination unit 14 obtains the variation rate of the data amount after the data conversion corresponding to the data conversion application, from the data conversion application information table 21. Next, in step S14, the determination unit 14 determines whether the obtained variation rate is 0 or more. When the variation rate is 0 or more, it is expected that the data amount tends to increase after the data conversion, and the processing shifts to step S15 in which the determination unit 14 temporarily sets the After characteristic as a characteristic of the data conversion application. On the other hand, when the variation rate is less than 0, it is expected that the data amount tends to decrease after the data conversion, and the processing shifts to step S16 in which the determination unit 14 temporarily sets the Before characteristic, as a characteristic of the data conversion application. For example, when the data conversion application is “APL_C”, since the variation rate is “5” which is 0 or more, the After characteristic is temporarily set as a characteristic of the data conversion application.
In the following processing, the characteristic that is temporarily set in step S15 or S16, is used in data conversion application whose characteristic managed by the data conversion application information table 21 is the Any characteristic.
Next, in step S17, the determination unit 14 obtains the load information of a candidate for the data conversion execution server, from the load information table 23, based on the characteristic of the data conversion application. Specifically, when the characteristic of the data conversion application is the Before characteristic, the transfer source server S is a candidate for the data conversion execution server. On the other hand, when the characteristic of the data conversion application is the After characteristic, the transfer destination server R is a candidate for the data conversion execution server. The determination unit 14 specifies a candidate for the data conversion execution server, based on the characteristic of the data conversion application and the information on the transfer source server S and the transfer destination server R which are designated by the execution instruction of the data transfer. For example, when the data conversion application is “APL_B”, since the characteristic of “APL_B” is the Before characteristic, the storage server 30A that is the transfer source server S which is designated by the execution instruction of the data transfer, is specified as a candidate. The determination unit 14 obtains the load information which is associated with the specified candidate for the data conversion execution server, with reference to the load information table 23.
Next, in step S18, based on the obtained load information, it is determined whether the load situation is small or not, by determining whether the load situation of the candidate of the data conversion execution server satisfies a predetermined condition or not. For example, the predetermined condition may be set such that the load situation is determined to be small when the concurrency number of data conversion applications is a predetermined number or less and the resource use situation is a predetermined value or less. The case where the resource use situation is the predetermined value or less, may be defined as a case where each of all the resource use situations is equal to or less than a threshold which is determined for the each resource. Furthermore, the condition is not limited to the above example. When the determination unit 14 has determined that the load situation of the candidate for the data conversion execution server is small, by comparing the load information with the condition, the processing shifts to step S19, and, when the determination unit 14 has determined that the load situation is large, the processing shifts to step S22 of
In step S19, the determination unit 14 determines whether or not the characteristic of the data conversion application is the Before characteristic. In the case of the Before characteristic, the processing shifts to step S20 in which the determination unit 14 determines the transfer source server S (here, the storage server 30A) which is the candidate for the data conversion execution server, as the data conversion execution server. On the other hand, when the characteristic of the data conversion application is the After characteristic, the processing shifts to step S21 in which the determination unit 14 determines the transfer destination server R (here, the storage server 30B) which is the candidate for the data conversion execution server, as the data conversion execution server.
When the processing shifts to step S22 by determining NO in step S18, the determination unit 14 determines whether or not the characteristic of the data conversion application is the Before characteristic. In the case of the Before characteristic, the processing shifts to step S23, and in the case of the After characteristic, the processing shifts to step S30 of
In step S23, the determination unit 14 obtains the load information of the transfer destination server R which is not the candidate for the data conversion execution server, from the load information table 23. Next, in step S24, by comparing the load situation which is indicated by the obtained load information with the predetermined condition in the same manner as step S18, the determination unit 14 determines whether or not the load situation of the transfer destination server R is small. When the load situation is small, the processing shifts to step S25, and when the load situation is large, the processing returns to step S12 of
In step S25, an incremental transfer time ΔtR that is a time increased by causing the transfer destination server R to convert the data, is calculated. Here, as illustrated in
The determination unit 14 obtains the data amount (data amount before the conversion) of the target data, with reference to the data conversion application actual result table 22. Moreover, the determination unit 14 obtains the variation rate of the data amount after the data conversion corresponding to the data conversion application, from the data conversion application information table 21. AS for the data conversion application without the actual result which is actually executed, since the statistical information thereof is not accumulated, the predetermined variation rate is used depending on the characteristic of the data conversion application. Furthermore, the determination unit 14 obtains the network transfer rate corresponding to the transfer source server S, from the load information table 23, and the determination unit 14 calculates the incremental transfer time ΔtR, by the following equation (1).
Δt
R=(TtR+TcR)−(TcS+TtS)=(the data amount of the target data×the network transfer rate)−(the data amount of the target data (1+the variation rate)×the network transfer rate) (1)
Next, in step S26, the determination unit 14 calculates the incremental conversion time ΔTcS that is an increment of the conversion time TcS resulting from increase in the load of the transfer source server S. Specifically, the determination unit 14 obtains the data throughput per unit time corresponding to the data conversion application, from the data conversion application information table 21. As for the data conversion application without the actual result which is actually executed, since the statistical information thereof is not accumulated, a predetermined data throughput per unit time is used depending on the characteristic of the data conversion application. Moreover, the determination unit 14 obtains each resource use situation corresponding to the transfer source server S, from the load information table 23, and obtains a coefficient k depending on the load situation of the transfer destination server R indicating each resource use situation, based on a predetermined correspondence relationship between the load situation and the coefficient k. For example, in the case of setting k at 1 for an initial conversion time that is required when the load situation of the storage server 30 is small (satisfies the condition), k times the initial conversion time may be set as a conversion time for each load situation. Furthermore, the load situation corresponding to the coefficient k, is not limited to the value using all the resource use situations, and for example, may be a value using only the use rate of the CPU. Therefore, the determination unit 14 calculates the incremental conversion time ΔTcS, by the following equation (2).
ΔTcS=(k−1)×TcS=(k−1)×(the data throughput per unit time×the data amount of the target data) (2)
Next, in step S27, the determination unit 14 determines whether or not the incremental conversion time ΔTcS calculated in step S26 is equal to or less than the incremental transfer time ΔtR calculated in step S25. Here, as illustrated in
When the processing shifts to step S30 of
In step S32, an incremental transfer time ΔtS obtained by causing the transfer source server S to convert the data is calculated. As illustrated in
The determination unit 14 calculates the incremental transfer time ΔtS, by the following equation (3), using the data amount of the target data which is obtained in step S25, the variation rate of the data amount after the data conversion corresponding to the data conversion application, and the network transfer rate corresponding to the transfer source server S.
Δt
S=(TcS+TtS)−(TtR+TcR)=(the data amount of the target data (1+the variation rate)×the network transfer rate)−(the data amount of the target data×the network transfer rate) (3)
Next, in step S33, the determination unit 14 calculates the incremental conversion time ΔTcR caused by increase in the load of the transfer destination server R. Specifically, the determination unit 14 obtains each resource use situation corresponding to the transfer destination server R, from the load information table 23, and obtains the coefficient k depending on the load situation of the transfer destination server R which is indicated by each resource use situation, based on the predetermined correspondence relationship between the load situation and the coefficient k. The determination unit 14 calculates the incremental conversion time ΔTcR, by the following equation (4).
ΔTc
R=(k−1)×TcR=(k−1)×(the data throughput per unit time×the data amount of the target data) (4)
Next, in step S34, the determination unit 14 determines whether or not the incremental conversion time ΔTcR calculated in step S33 is equal to or less than the incremental transfer time ΔtS calculated in step S32. Here, as illustrated in
The case of determining NO in step S24 or S31 is a case that the load situations of all of the transfer source server S and the transfer destination server R are large. In this case, by returning to step S12, the determination of the data conversion execution server is suspended. When the load situation of any one of the transfer source server S and the transfer destination server R becomes small while returning to step S12 and repeating the processes after step S13, the data conversion execution server is determined. Furthermore, at the time of returning to step S12 by determining NO in step S24 or S31, a predetermined standby time may be set.
As described above, according to the transfer control device 10 relating to the first embodiment, the characteristic indicating the variation in data amount before and after the data conversion for the data conversion application to be executed, the statistical information at the time of executing the data conversion application, and the load information of the storage server, are managed. Then, the candidate for the data conversion execution server is specified, based on the characteristic of the data conversion application. Based on the load information, the load situation of the candidate is determined, and when the load situation indicates a small load, the candidate is determined as a data conversion execution server. Additionally, when the load situation of the candidate indicates a large load, and the load situation of the storage server which is not the candidate indicates a small load, the storage server whose efficiency is better is determined as a data conversion execution server, by comparing the efficiencies of the data transfer in both of the statistical information and the load information, based on the statistical information and the load information. Hereby, it is possible to improve the data transfer efficiency of the data transfer which is accompanied with the data conversion between the storage servers.
Next, a second embodiment will be described. Since a configuration of a transfer control device 10 according to the second embodiment is the same as the transfer control device 10 according to the first embodiment, the description thereof will be omitted.
In the first embodiment, it is described the case that the determination of the data conversion execution server is suspended when the load situations of both the transfer source server S and the transfer destination server R are large. In the second embodiment, even when the load situations of both the transfer source server S and the transfer destination server R are large, by comparing the efficiencies of the data transfer in both the transfer source server S and the transfer destination server R, the storage server whose efficiency is better is determined as a data conversion execution server. Hereinafter, with reference to
In a case of determining NO in step S24 of
Next, in step S43, the determination unit 14 calculates the incremental conversion time ΔTcR caused by increase in the load of the transfer destination server R, in the same manner as step S33. As illustrated in
Moreover, in a case of determining NO in step S31 of
Next, in step S47, the determination unit 14 calculates the incremental conversion time ΔTcS caused by increase in the load of the transfer source server S, in the same manner as step S26. As illustrated in
As described above, according to the transfer control device 10 relating to the second embodiment, even when the loads of both the transfer source server S and the transfer destination server R are large, the storage server whose efficiency is better is determined as a data conversion execution server, by comparing the efficiencies of the data transfer in both the transfer source server S and the transfer destination server R. Hereby, it is possible to improve the data transfer efficiency of the data transfer which is accompanied with the data conversion between the storage servers, in the same manner as the first embodiment.
In the above embodiments, a form in which the transfer control program 50 is stored (installed) in advance in the storage unit 46 is described, but it is not limited thereto. It is possible to provide a form of recording the transfer control program 50 in the storage medium such as a CD-ROM, a DVD-ROM, a USB memory or the like.
All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a showing of the superiority and inferiority of the invention. Although the embodiments of the present invention have been described in detail, it should be understood that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the invention.
Number | Date | Country | Kind |
---|---|---|---|
2014-083060 | Apr 2014 | JP | national |