CN117331691A - Method, device, server and medium for distributing central processing unit cores - Google Patents

Method, device, server and medium for distributing central processing unit cores Download PDF

Info

Publication number
CN117331691A
CN117331691A CN202311278554.3A CN202311278554A CN117331691A CN 117331691 A CN117331691 A CN 117331691A CN 202311278554 A CN202311278554 A CN 202311278554A CN 117331691 A CN117331691 A CN 117331691A
Authority
CN
China
Prior art keywords
service
service group
cpu cores
cpu
group
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202311278554.3A
Other languages
Chinese (zh)
Inventor
张攀
过晓春
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China United Network Communications Group Co Ltd
Unicom Digital Technology Co Ltd
Unicom Cloud Data Co Ltd
Original Assignee
China United Network Communications Group Co Ltd
Unicom Digital Technology Co Ltd
Unicom Cloud Data Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China United Network Communications Group Co Ltd, Unicom Digital Technology Co Ltd, Unicom Cloud Data Co Ltd filed Critical China United Network Communications Group Co Ltd
Priority to CN202311278554.3A priority Critical patent/CN117331691A/en
Publication of CN117331691A publication Critical patent/CN117331691A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Hardware Redundancy (AREA)

Abstract

The application provides a method, a device, a server and a medium for distributing central processing unit cores. In the method, a scene type of each service and/or an importance level of each service are obtained in response to an allocation request; dividing a plurality of services into a plurality of service groups according to the scene type of each service and/or the importance level of each service; at least one central processing unit CPU core is allocated for each service group. The method for distributing the fixed CPU cores for each service in the prior art solves the problem that once explosive flow occurs to a certain service, a fixed number of CPU cores are used, and normal operation of the service cannot be met.

Description

Method, device, server and medium for distributing central processing unit cores
Technical Field
The present invention relates to the field of server technologies, and in particular, to a method, an apparatus, a server, and a medium for distributing a central processing unit core.
Background
A central processing unit (Central Processing Unit, abbreviated as CPU) is one of the core components of the server, responsible for performing computing tasks and processing data. The physical cores of the CPU may be split into multiple virtual CPU cores, each of which may independently execute instructions and process data as one physical core.
A service refers to a program, routine, or process that performs a specified system function. Each service needs to rely on at least one CPU core at runtime. In the prior art, a fixed number of CPU cores are typically assigned to each service.
However, in the method of allocating a fixed CPU core to each service in the prior art, once burst traffic occurs in a certain service, a problem that a fixed number of CPU cores are used and normal operation of the service cannot be satisfied occurs.
Disclosure of Invention
The application provides a method, a device, a server and a medium for distributing CPU cores, which are used for solving the problem that once explosive flow occurs to a certain service, a fixed number of CPU cores are used and normal operation of the service cannot be met in the method for fixing the CPU cores for each service in the prior art.
In a first aspect, the present application provides a method of allocating a central processing unit core, comprising:
acquiring a scene type of each service and/or an importance level of each service in response to the allocation request;
dividing a plurality of services into a plurality of service groups according to the scene type of each service and/or the importance level of each service;
At least one central processing unit CPU core is allocated for each service group.
In one implementation, the assigning at least one central processing unit CPU core to each service group includes:
for each service group, determining the number of CPU cores corresponding to the service group according to the importance level of each service in the service group and the number of the services in the service group;
and distributing at least one CPU core to each service group according to the number of the CPU cores corresponding to each service group.
In one implementation manner, the allocating at least one CPU core for each service group according to the number of CPU cores corresponding to each service group includes:
acquiring the total number of CPU cores;
according to the number of the CPU cores corresponding to each service group, calculating the total number of the CPU cores corresponding to a plurality of service groups;
under the condition that the total number of CPU cores is identified to be smaller than the total number of CPU cores corresponding to the plurality of service groups, determining the CPU cores corresponding to each service group according to the number of the CPU cores corresponding to each service group, the total number of the CPU cores and the importance level of each service in each service group; wherein, at least one CPU core corresponding to at least one service group is the same as at least one CPU core corresponding to other service groups;
And distributing the CPU cores corresponding to each service group for each service group.
In one implementation, the method further comprises:
after the CPU core corresponding to each service group is allocated to each service group, the same priority is allocated to each service group;
for each service group, when identifying that the competing service group of the service groups exists in the plurality of service groups, adjusting the priority of the service group or the priority of the competing service group according to the importance level of each service in the service group and the importance level of each service in the competing service group; wherein, at least one CPU core allocated to the competing service group is the same as at least one CPU core allocated to the service group.
In one implementation, the method further comprises:
acquiring historical utilization rate of CPU cores corresponding to each service group;
for each service group, processing the historical use rate of the CPU core corresponding to the service group by utilizing a prediction model to obtain the predicted use rate of the CPU core corresponding to the service group;
and for each service group, adjusting the number of the CPU cores corresponding to the service group according to the predicted utilization rate of the CPU cores corresponding to the service group.
In one implementation manner, for each service group, the adjusting the number of CPU cores corresponding to the service group according to the predicted usage rate of the CPU cores corresponding to the service group includes:
and for each service group, when the predicted utilization rate of the CPU cores corresponding to the service group is recognized to exceed a preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the service group, the preset range and the number of the CPU cores corresponding to the service group.
In one implementation, the predicted usage of the CPU cores corresponding to the service group includes predicted usage of the CPU cores corresponding to the service group for a plurality of time periods;
when recognizing that the predicted utilization rate of the CPU cores corresponding to the service group exceeds a preset range for each service group, adjusting the number of the CPU cores corresponding to the service group according to the predicted utilization rate of the CPU cores corresponding to the service group, wherein the preset range and the number of the CPU cores corresponding to the service group comprises:
for each service group, determining the predicted utilization rate of the CPU core corresponding to the target time period according to the predicted utilization rates of the CPU cores of a plurality of time periods corresponding to the service group; the target time period is a time period acquired in advance;
When the predicted utilization rate of the CPU cores corresponding to the target time period is recognized to exceed the preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the target time period, the preset range and the number of the CPU cores corresponding to the service group.
In one implementation, the method further comprises:
for each service group, after the number of CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the service group, judging whether a competing service group of the service groups exists in the service groups or not;
and when judging that the competing service groups of the service groups exist in the plurality of service groups, adjusting the priority of the service groups or the priority of the competing service groups according to the importance level of each service in the service groups and the importance level of each service in the competing service groups.
In a second aspect, an embodiment of the present application provides an apparatus for allocating a central processing unit core, including:
the acquisition module is used for responding to the allocation request and acquiring the scene type of each service and/or the importance level of each service;
The processing module is used for dividing the plurality of services into a plurality of service groups according to the scene type of each service and/or the importance level of each service;
the processing module is further configured to allocate at least one central processing unit CPU core for each service group.
In one implementation, the processing module is specifically configured to:
for each service group, determining the number of CPU cores corresponding to the service group according to the importance level of each service in the service group and the number of the services in the service group;
and distributing at least one CPU core to each service group according to the number of the CPU cores corresponding to each service group.
In one implementation, the processing module is specifically configured to:
acquiring the total number of CPU cores;
according to the number of the CPU cores corresponding to each service group, calculating the total number of the CPU cores corresponding to a plurality of service groups;
under the condition that the total number of CPU cores is identified to be smaller than the total number of CPU cores corresponding to the plurality of service groups, determining the CPU cores corresponding to each service group according to the number of the CPU cores corresponding to each service group, the total number of the CPU cores and the importance level of each service in each service group; wherein, at least one CPU core corresponding to at least one service group is the same as at least one CPU core corresponding to other service groups;
And distributing the CPU cores corresponding to each service group for each service group.
In one implementation, the processing module is further configured to:
after the CPU core corresponding to each service group is allocated to each service group, the same priority is allocated to each service group;
for each service group, when identifying that the competing service group of the service groups exists in the plurality of service groups, adjusting the priority of the service group or the priority of the competing service group according to the importance level of each service in the service group and the importance level of each service in the competing service group; wherein, at least one CPU core allocated to the competing service group is the same as at least one CPU core allocated to the service group.
In one implementation, the processing module is further configured to:
acquiring the historical utilization rate of a CPU core of a central processing unit corresponding to each service group;
for each service group, processing the historical use rate of the CPU core corresponding to the service group by utilizing a prediction model to obtain the predicted use rate of the CPU core corresponding to the service group;
and for each service group, adjusting the number of the CPU cores corresponding to the service group according to the predicted utilization rate of the CPU cores corresponding to the service group.
In one implementation, the processing module is specifically configured to:
and for each service group, when the predicted utilization rate of the CPU cores corresponding to the service group is recognized to exceed a preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the service group, the preset range and the number of the CPU cores corresponding to the service group.
In one implementation, the predicted usage of the CPU cores corresponding to the service group includes predicted usage of the CPU cores corresponding to the service group for a plurality of time periods;
the processing module is specifically configured to:
for each service group, determining the predicted utilization rate of the CPU core corresponding to the target time period according to the predicted utilization rates of the CPU cores of a plurality of time periods corresponding to the service group; the target time period is a time period acquired in advance;
when the predicted utilization rate of the CPU cores corresponding to the target time period is recognized to exceed the preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the target time period, the preset range and the number of the CPU cores corresponding to the service group.
In one implementation, the processing module is further configured to:
for each service group, after the number of CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the service group, judging whether a competing service group of the service groups exists in the service groups or not;
and when judging that the competing service groups of the service groups exist in the plurality of service groups, adjusting the priority of the service groups or the priority of the competing service groups according to the importance level of each service in the service groups and the importance level of each service in the competing service groups.
In a third aspect, the present application provides a server comprising:
a processor, and a memory communicatively coupled to the processor;
the memory is used for storing computer execution instructions;
the processor is configured to execute the computer-executable instructions stored in the memory to implement the method for allocating a central processing unit core according to the first aspect.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, are configured to implement the method for allocating a central processor core according to the first aspect.
The application provides a method, a device, a server and a medium for distributing central processing unit cores. In the method, a plurality of services may be divided into a plurality of service groups according to a scene type of each service and/or an importance level of each service, and at least one CPU core may be allocated to each service group. By the mode of flexibly configuring the CPU core for each service, the CPU core bound by the service can be simplified and simultaneously proper buffer resources are provided for the service to use the CPU core, so that the condition that the service is abnormal due to the sudden increase of the demand of the single service on the CPU core is avoided. The method for distributing the fixed CPU cores for each service in the prior art solves the problem that once explosive flow occurs to a certain service, a fixed number of CPU cores are used, and normal operation of the service cannot be met.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief description of the drawings used in the description of the embodiments or the prior art will be provided below.
FIG. 1a is a flowchart illustrating a method for allocating CPU cores according to an embodiment of the present disclosure;
FIG. 1b is a schematic diagram of a method for allocating CPU cores according to an embodiment of the present application;
FIG. 2a is a flowchart illustrating a second embodiment of a method for allocating CPU cores according to the present disclosure;
FIG. 2b is a schematic diagram of another method for allocating CPU cores according to an embodiment of the present application;
FIG. 3a is a flowchart illustrating a third embodiment of a method for allocating CPU cores according to the present disclosure;
fig. 3b is a schematic view of a cpu core corresponding to an adjustment service set according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating a method for allocating CPU cores according to a fourth embodiment of the present disclosure;
FIG. 5 is a flowchart of a fifth embodiment of a method for allocating CPU cores according to the present disclosure;
FIG. 6 is a schematic structural diagram of an embodiment of a central processing core distribution device according to the present application;
fig. 7 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments will be clearly and completely described below with reference to the accompanying drawings in the embodiments, and the described embodiments are some embodiments of the present application, but not all embodiments. Based on the embodiments of the present application, other embodiments made by a person skilled in the art in light of the teachings of the present embodiments are all within the scope of the protection of the present application.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims of this application and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements that are expressly listed or inherent to such process, method, article, or apparatus.
A central processing unit (Central Processing Unit, abbreviated as CPU) is one of the core components of the server, responsible for performing computing tasks and processing data. The physical cores of the CPU may be split into multiple virtual CPU cores, each of which may independently execute instructions and process data as one physical core. A service refers to a program, routine, or process that performs a specified system function. Each service needs to rely on at least one CPU core at runtime. In the prior art, a fixed number of CPU cores is typically specified for each service by fixing the number of CPU cores. However, in the method for fixing the number of CPU cores in the prior art, once burst traffic occurs in a service, a problem that the normal operation of the service cannot be satisfied because the fixed number of CPU cores are used.
Based on the technical problems, the technical conception of the application is as follows: the plurality of services is divided into a plurality of service groups, with each service group being assigned at least one CPU core. By the method, buffer resources (CPU cores) can be provided for the services, so that the services in the service group can still operate normally when explosive traffic occurs.
The scheme of allocating the cpu core of the present application is described in detail below. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.
Fig. 1a is a flowchart of a first embodiment of a method for allocating cpu cores according to an embodiment of the present application. Referring to fig. 1a, the method specifically comprises the steps of:
s101: in response to the allocation request, a scene type of each service and/or an importance level of each service is acquired.
In this embodiment, the server may acquire the scene type of each service and/or the importance level of each service in response to the allocation request sent by the terminal device.
S102: the plurality of services are divided into a plurality of service groups according to scene type of each service and/or importance level of each service.
In this embodiment, the server may divide the plurality of services into a plurality of service groups according to a scene type of each service and/or an importance level of each service.
In one implementation, the server may divide the plurality of services into a plurality of service groups according to a scene type of each service.
Taking a supersusion system as an example, in the supersusion system, common services include sshd (remote control service), crond (timing service), kernel (kernel service), systemmd (system service), SDS (software defined storage service), SDN (software defined network service), vms (virtual machine service), points (container group service), apps (application program service), MGR-OP (network monitoring service).
Fig. 1b is a schematic diagram of a scenario of a method for allocating a central processing unit core according to an embodiment of the present application. As shown in fig. 1b, the server may divide service 1 (sshd), service 2 (crond), service 3 (kernel), and service 4 (system) into system service groups (group-sys) based on the scene type of each service; dividing service 5 (SDS) into distributed storage service groups (group-SDS); dividing services 6 (SDN) into distributed network service groups (groups-SDNs); dividing service 7 (vms), service 8 (points), and service 9 (apps) into business service groups (group-vms); the service 10 (MGR-OP) is divided into management traffic service groups (group-MGR).
In one implementation, the server may divide the plurality of services into a plurality of service groups according to an importance level of each service.
For example, for services with importance levels of the first and second levels, the server may divide them into one service group individually; for the services with the importance levels of the third level to the fifth level, the server can divide the plurality of services into a service group according to the first preset number; for the services with the importance levels of the sixth level to the tenth level, the server may divide the plurality of services into one service group according to the second preset number. Wherein the first preset number is smaller than the second preset number.
In one implementation, the server may divide the plurality of services into a plurality of service groups according to a scene type of each service and an importance level of each service.
For example, for services with importance levels of the first and second levels, the server may divide them into one service group individually; for the services with the importance level of the third level to the fifth level, the server can divide the plurality of services into a service group according to the first preset number and the scene type of each service; for the services with the importance levels of the sixth level to the tenth level, the server may divide the plurality of services into one service group according to the second preset number and the scene type of each service.
S103: at least one CPU core is allocated for each service group.
In this embodiment, the server may allocate at least one CPU core for each service group after dividing the plurality of services into a plurality of service groups.
In one implementation, a fixed number of CPU cores may be allocated for each service group.
In one implementation, for each service group, the server may determine, according to the importance level of each service in the service group and the number of services in the service group, the number of CPU cores corresponding to the service group. After calculating the number of the CPU cores corresponding to each service group, the server may allocate the CPU cores to each service group according to the number of the CPU cores corresponding to each service group.
For example, taking service group including service 1, service 2, service 3 and service 4 as an example, based on the importance level of service 1 being the third level (coefficient is 0.8), the importance level of service 2 being the third level (coefficient is 0.8), the importance level of service 3 being the third level (coefficient is 0.8), the importance level of service 4 being the fifth level (coefficient is 0.6), the server may determine that the number of CPU cores corresponding to the service group is 3 (0.8x1+0.8x1+0.8x1+0.6x1=3). The server may allocate three CPU cores for the service group according to the number of CPU cores corresponding to the service group being 3.
It should be noted that the server may also obtain the total number of CPU cores. The server may calculate the total number of CPU cores corresponding to the plurality of service groups according to the number of CPU cores corresponding to each service group. The server may identify whether the total number of CPU cores is less than the total number of CPU cores corresponding to the plurality of service groups. The server determines that at least one CPU core needs to be allocated to at least two service groups when recognizing that the total number of CPU cores is smaller than the total number of CPU cores corresponding to the plurality of service groups.
Specifically, the server may determine the CPU core corresponding to each service group according to the number of CPU cores corresponding to each service group, the total number of CPU cores, and the importance level of each service in each service group. After determining the CPU core corresponding to each service group, the server may allocate the CPU core corresponding to the service group to each service group. Wherein at least one CPU core corresponding to at least one service group is identical to at least one CPU core corresponding to other service groups.
The server may illustratively determine the service group assigned to the same CPU core as the other service groups in the following manner. Specifically, the server may calculate the importance level of each service group according to the importance level of each service in each service group. The server may sort the importance levels of each service group in order from high to low, and select a service group having a lower importance level among the plurality of service groups as a service group allocated to the same CPU core as other service groups.
The beneficial effects of this embodiment are: the server may divide the plurality of services into a plurality of service groups according to scene type of each service and/or importance level of each service, and allocate at least one CPU core for each service group. By the mode of flexibly configuring the CPU cores for each service, the CPU cores bound by the service can be simplified and simultaneously proper buffer resources are provided for the service to use the CPU cores, so that the problem that once the service has explosive flow, a fixed number of CPU cores are used and normal operation of the service cannot be maintained in the method for distributing the fixed CPU cores for the service in the prior art is solved.
Fig. 2a is a flowchart of a second embodiment of a method for allocating cpu cores according to the present application. Referring to fig. 2a, the method specifically comprises the steps of:
s201: in response to the allocation request, a scene type of each service and/or an importance level of each service is acquired.
In this embodiment, the server may acquire the scene type of each service and/or the importance level of each service in response to the allocation request. The specific implementation process is the same as S101, and will not be described here again.
S202: the plurality of services are divided into a plurality of service groups according to scene type of each service and/or importance level of each service.
In the present embodiment, the server divides the plurality of services into a plurality of service groups according to the scene type of each service and/or the importance level of each service. The specific implementation process is the same as S102, and will not be described here again.
S203: at least one CPU core is allocated for each service group.
In this embodiment, the server may allocate at least one CPU core for each service group. The specific implementation process is the same as S103, and will not be described here again.
S204: after the CPU core corresponding to each service group is allocated to each service group, the same priority is configured for each service group.
In this embodiment, after allocating a CPU core corresponding to each service group, the server may configure the same priority for each server. For example, the server may configure a Priority (PR) of 1024 for each service group.
Fig. 2b is a schematic diagram of a scenario of another method for allocating a central processing unit core according to an embodiment of the present application. As shown in fig. 2b, the system service group (group-sys) includes four services, namely, service 1 (sshd), service 2 (crond), service 3 (kernel), and service 4 (system d); a distributed storage service group (group-SDS) includes service 5 (SDS); a distributed network service group (group-sn) includes a service 6 (SDN); the business service group (group-vms) comprises three services, namely a service 7 (vms), a service 8 (points) and a service 9 (apps); the management traffic service group (group-MGR) includes service 10 (MGR-OP).
The identities of the three CPU cores corresponding to the system service group are respectively 0-2. The priority of the system service group is 1024. The identities of the thirteen CPU cores corresponding to the distributed storage service group are 3-15. The distributed storage service group has a priority of 1024. The identities of the four CPU cores corresponding to the distributed network service group are 16-19. The priority of the distributed network service group is 1024. The identities of forty CPU cores corresponding to the business service group are 25-64. The business service group has a priority of 1024. The identity of five CPU cores corresponding to the management service group is 20-24. The priority of managing business service groups is 1024.
S205: and for each service group, when the competing service groups of the service groups exist in the plurality of service groups are identified, adjusting the priority of the service groups and/or the priority of the competing service groups according to the importance level of each service in the service groups and the importance level of each service in the competing service groups.
In this embodiment, for each service group, the server may identify whether there is a competing service group of the service groups among the plurality of service groups. Wherein the at least one CPU core to which the competing service group is assigned is the same as the at least one CPU core to which the service group is assigned.
When the server identifies that the competing service groups of the service groups exist in the plurality of service groups, the priority of the service groups and/or the competing service groups is adjusted according to the importance level of each service in the service groups and the importance level of each service in the competing service groups.
For example, upon identifying that a competing service group, a third service group, of the plurality of service groups exists, the server may determine that the importance level of the service in the first service group is higher than the importance level of the service in the second service group based on the importance level of each service in the first service group (third and fourth levels, respectively) and the importance level of each service in the third service group (fourth and fifth levels, respectively). The server adjusts the priority of the first service group from 1024 to 8192 so that the priority of the first service group is higher than the priority of the third service group.
In this embodiment, for each service group, when identifying that there is a competing service group of the service groups in the plurality of service groups, the server adjusts the priority of the service group and/or the priority of the competing service group according to the importance level of each service in the service group and the importance level of each service in the competing service group, so as to avoid the situation that when the plurality of service groups are allocated to the same CPU core, the service group composed of a plurality of services with higher importance levels cannot compete against the CPU core when the CPU core is required to be used, resulting in the failure of normal operation of the key service.
Fig. 3a is a flowchart illustrating a third embodiment of a method for allocating cpu cores according to an embodiment of the present application. Referring to fig. 3a, the method specifically comprises the steps of:
s301: and acquiring the historical utilization rate of the CPU core corresponding to each service group.
In this embodiment, the server may divide a plurality of services into a plurality of service groups each including at least one service in advance. Each service group corresponds to (binds) at least one CPU core.
For each service group, the server may use a monitor (software) to collect the historical usage rate of the CPU core corresponding to each service group once every set period of time.
The following describes a process of collecting data from the server.
In one acquisition process, for each service group, the server may acquire a historical usage rate of each CPU core corresponding to the service group. Wherein the historical usage of each CPU core represents the proportion of time that the CPU core occupies over a period of time. For example, a CPU core has a historical usage of 50% indicating that there is 50% of the time that the CPU core is in an idle state and 50% of the time that the CPU core is in a compute state. For each service group, after obtaining the historical usage rate of each CPU core corresponding to the service group, the server may perform an averaging process on the historical usage rate of at least one CPU core corresponding to the service group, and determine the historical usage rate of the CPU core corresponding to the service group in a collecting process.
After the multiple collection process, for each service group, the server may aggregate the multiple collected historical usage rates of the CPU cores corresponding to the service group to determine the historical usage rate (time-series data set) of the CPU cores corresponding to the service group. When a data missing condition occurs, the server may supplement the missing data by an average filling method.
The server may acquire a historical usage rate (time-series data set) of CPU cores corresponding to each service group acquired in advance when the number of CPU cores needs to be adjusted.
In one implementation, the server may obtain the historical usage of the CPU core corresponding to each service group in response to the obtained adjustment request.
In one implementation, the server may obtain a historical usage rate of the CPU core corresponding to each service group when it detects that the current time period is in the timing adjustment time period.
S302: and processing the utilization rate of the CPU cores corresponding to the service groups by utilizing a prediction model aiming at each service group, and obtaining the predicted utilization rate of the CPU cores corresponding to the service groups.
In the present embodiment, there is a periodic feature due to the usage rate of the CPU core corresponding to each service group.
For each service group, the server may process the historical usage (time-series data set) of the CPU core corresponding to the service group by using the prediction model after obtaining the historical usage of the CPU core corresponding to the service group, to obtain the predicted usage of the CPU core corresponding to the service group.
For example, the server may process the historical usage rate of the CPU core corresponding to the service group by using the trained cubic exponential smoothing model, to obtain the predicted usage rate of the CPU core corresponding to the service group. The trained three-time exponential smoothing model is obtained by training the prediction model by the server according to the use data of the CPU cores corresponding to each service group of the super fusion system and adjusting model parameters of the prediction model.
S303: and for each service group, adjusting the number of the CPU cores corresponding to the service group according to the predicted utilization rate of the CPU cores corresponding to the service group.
In this embodiment, for each service group, after obtaining the predicted usage rate of the CPU core corresponding to the service group, the server may adjust the number of CPU cores corresponding to the service group according to the predicted usage rate of the CPU core corresponding to the service group.
Specifically, for each service group, the server may determine whether the predicted usage of the CPU core corresponding to the service group exceeds a preset range. When judging that the predicted utilization rate of the CPU cores corresponding to the service group exceeds the preset range, the server adjusts the number of the CPU cores corresponding to the service group according to the predicted utilization rate of the CPU cores corresponding to the service group, the preset range and the number of the CPU cores corresponding to the service group.
In addition, for each service group, the server can also judge whether a competing service group of the service groups exists or not after adjusting the number of the CPU cores corresponding to the service groups according to the predicted utilization rate of the CPU cores corresponding to the service groups; the CPU cores corresponding to the service groups are the same as the CPU cores corresponding to the competing service groups. When judging that the competing service groups of the service groups exist in the plurality of service groups, the server can adjust the priority of the service groups or the priority of the competing service groups according to the importance level of each service in the service groups and the importance level of each service in the competing service groups so as to avoid the situation that the service groups with higher service importance levels cannot compete to the CPU core and further the service in the service groups with higher service importance levels cannot normally run.
Fig. 3b is a schematic view of a cpu core corresponding to an adjustment service set according to an embodiment of the present application. As shown in fig. 3b, the system service group (group-sys) includes four services, namely, service 1 (sshd), service 2 (crond), service 3 (kernel), and service 4 (system d); a distributed storage service group (group-SDS) includes service 5 (SDS); a distributed network service group (group-sn) includes a service 6 (SDN); the business service group (group-vms) comprises three services, namely a service 7 (vms), a service 8 (points) and a service 9 (apps); the management traffic service group (group-MGR) includes service 10 (MGR-OP).
Before adjustment:
the identities of the three CPU cores corresponding to the system service group are respectively 0-2. The priority of the system service group is 1024.
The identities of the thirteen CPU cores corresponding to the distributed storage service group are 3-15. The distributed storage service group has a priority of 1024.
The identities of the four CPU cores corresponding to the distributed network service group are 16-19. The priority of the distributed network service group is 1024.
The identities of forty CPU cores corresponding to the business service group are 25-64. The business service group has a priority of 1024.
The identity of five CPU cores corresponding to the management service group is 20-24. The priority of managing business service groups is 1024.
After adjustment:
the identities of the three CPU cores corresponding to the system service group are respectively 0-2. The priority of the system service group is 8192.
The identities of six CPU cores corresponding to the distributed storage service group are 3-8. The priority of the distributed storage service group is 8192.
The identities of the four CPU cores corresponding to the distributed network service group are 9-12. The priority of the distributed network service group is 8192.
The identities of fifty-two CPU cores corresponding to the business service group are 13-64. The business service group has a priority of 1024.
The identities of ten CPU cores corresponding to the management service group are 3-12. The priority of managing business service groups is 1024.
In this embodiment, the server may predict the predicted usage rate of the CPU core corresponding to the service group based on the historical usage rate of the CPU core corresponding to the service group, so as to adjust the number of CPU cores corresponding to the service group in advance according to the predicted usage rate of the CPU core corresponding to the service group, thereby ensuring the number of CPU cores bound by the service group, and meeting the normal operation of the service in the service group.
Fig. 4 is a flowchart of a fourth embodiment of a method for allocating a cpu core according to the present application. Referring to fig. 4, the method specifically includes the steps of:
S401: and acquiring the historical utilization rate of the CPU core corresponding to each service group.
In this embodiment, the server may acquire the historical usage rate of the CPU core corresponding to each service group. The specific implementation process is the same as S301, and will not be described here again.
S402: and processing the utilization rate of the CPU cores corresponding to the service groups by utilizing a prediction model aiming at each service group, and obtaining the predicted utilization rate of the CPU cores corresponding to the service groups.
In this embodiment, for each service group, the server may process the usage rate of the CPU core corresponding to the service group by using the prediction model, and obtain the predicted usage rate of the CPU core corresponding to the service group. The specific implementation process is the same as S302, and will not be described here again.
S403: and for each service group, when the predicted utilization rate of the CPU cores corresponding to the service group is recognized to exceed a preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the service group, the preset range and the number of the CPU cores corresponding to the service group.
In this embodiment, for each service group, the server may identify whether the predicted usage rate of the CPU core corresponding to the service group exceeds a preset range.
When the server identifies that the predicted utilization rate of the CPU cores corresponding to the service group exceeds a preset range, determining the number of the CPU cores corresponding to the service group, and not matching with the requirements of the service group in a future time period.
The server can adjust the number of the CPU cores corresponding to the service group according to the predicted utilization rate of the CPU cores corresponding to the service group, the preset range and the number of the CPU cores corresponding to the service group.
In one implementation, the server may calculate the difference rate according to the predicted usage rate of the CPU core corresponding to the service group and the preset range. The server can calculate the number of CPU cores corresponding to the adjusted service group according to the difference rate and the number of CPU cores corresponding to the service group. The service group can adjust the number of the CPU cores corresponding to the service group according to the number of the CPU cores corresponding to the adjusted service group. That is, the server may reassign the service group to at least one CPU core according to the number of CPU cores corresponding to the adjusted service group.
By way of specific example, the process of adjusting the number of central processor cores is described below.
For example, taking the preset range of [30% -40% ] as an example, when the server calculates that the predicted usage rate of the CPU core corresponding to the service group is 50%, it can be identified that the predicted usage rate of the CPU core corresponding to the service group is greater than the preset range. The server may adjust the number of CPU cores corresponding to the service group from 3 to 4 according to the predicted usage rate of CPU cores corresponding to the service group being 50%, the preset range being [30% -40% ], and the number of CPU cores corresponding to the service group being 3. By the method, the situation that the CPU cores bound by the service group have waste in the future time period can be avoided.
For another example, taking the preset range as [30% -40% ] as an example, when the server calculates that the predicted usage rate of the CPU core corresponding to the service group is 20%, it can be identified that the predicted usage rate of the CPU core corresponding to the service group is smaller than the preset range. The server may adjust the number of CPU cores corresponding to the service group from 3 to 2 according to the predicted usage rate of CPU cores corresponding to the service group being 20%, the preset range being [30% -40% ], and the number of CPU cores corresponding to the service group being 3. By the method, the situation that the CPU cores bound by the service group are overloaded in a future time period can be avoided.
In this embodiment, for each service group, when the server identifies that the predicted usage rate of the CPU core corresponding to the service group exceeds the preset range, the number of CPU cores corresponding to the service group is adjusted according to the predicted usage rate of the CPU core corresponding to the service group, the preset range and the number of CPU cores corresponding to the service group, so that the number of CPU cores corresponding to the adjusted service group can meet the requirements of the service group, and thus the situation that the CPU cores bound by the service group have overload or waste in a future time period is avoided.
Fig. 5 is a flowchart of a fifth embodiment of a method for allocating a cpu core according to the present application. Referring to fig. 5, the method specifically includes the steps of:
s501: and acquiring the historical utilization rate of the CPU core corresponding to each service group.
In this embodiment, the server may acquire the historical usage rate of the CPU core corresponding to each service group. The specific implementation process is the same as S301, and will not be described here again.
S502: and processing the utilization rate of the CPU cores corresponding to the service groups by utilizing a prediction model aiming at each service group, and obtaining the predicted utilization rate of the CPU cores corresponding to the service groups.
In this embodiment, for each service group, the server may process the usage rate of the CPU core corresponding to the service group by using the prediction model, and obtain the predicted usage rate of the CPU core corresponding to the service group. The predicted utilization rate of the CPU core corresponding to the service group comprises the predicted utilization rates of the CPU cores corresponding to the service group in a plurality of time periods.
S503: for each service group, determining the predicted utilization rate of the CPU core corresponding to the target time period according to the predicted utilization rates of the CPU cores of the plurality of time periods corresponding to the service group.
In this embodiment, the server may acquire the target period in advance. For example, the target time period may be 20:00-22:00. Wherein the target time period is a time period specified by a user.
For each service group, the server may determine a predicted usage of the CPU core corresponding to the target time period from predicted usages of the CPU cores of the plurality of time periods corresponding to the service group.
S504: when the predicted utilization rate of the CPU cores corresponding to the target time period is recognized to exceed the preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the target time period, the preset range and the number of the CPU cores corresponding to the service group.
In this embodiment, the server may identify whether the predicted usage rate of the CPU core corresponding to the target period of time exceeds a preset range.
When the server recognizes that the predicted utilization rate of the CPU cores corresponding to the target time period exceeds the preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the target time period, the preset range and the number of the CPU cores corresponding to the service group.
The beneficial effects of this embodiment are: the server may determine the predicted utilization rate of the CPU cores corresponding to the target time period according to the predicted utilization rates of the CPU cores corresponding to the service group in a plurality of time periods, and adjust the number of CPU cores corresponding to the service group when it is identified that the predicted utilization rate of the CPU cores corresponding to the target time period exceeds a preset range. Through the mode, the number of the CPU cores corresponding to the service group can be ensured to meet the requirement of the service group in the appointed target time period, and then the normal operation of the service is ensured.
The following are device embodiments of the present application, which may be used to perform method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.
FIG. 6 is a schematic structural diagram of an embodiment of a central processing core distribution device according to the present application; as shown in fig. 6, the apparatus 60 for allocating a central processing unit core includes: an acquisition module 61 and a processing module 62; wherein, the obtaining module 61 is configured to obtain a scene type of each service and/or an importance level of each service in response to the allocation request; a processing module 62, configured to divide the plurality of services into a plurality of service groups according to a scene type of each service and/or an importance level of each service; the processing module 62 is further configured to allocate at least one central processing unit CPU core for each service group.
The device for distributing the central processing unit core provided by the embodiment of the application can execute the technical scheme shown in the embodiment of the method, and the implementation principle and the beneficial effects are similar, and are not repeated here.
In one implementation, the processing module 62 is specifically configured to: for each service group, determining the number of CPU cores corresponding to the service group according to the importance level of each service in the service group and the number of the services in the service group; and distributing at least one CPU core to each service group according to the number of the CPU cores corresponding to each service group.
The device for distributing the central processing unit core provided by the embodiment of the application can execute the technical scheme shown in the embodiment of the method, and the implementation principle and the beneficial effects are similar, and are not repeated here.
In one implementation, the processing module 62 is specifically configured to: acquiring the total number of CPU cores; according to the number of CPU cores corresponding to each service group, calculating the total number of CPU cores corresponding to a plurality of service groups; under the condition that the total number of CPU cores is identified to be smaller than the total number of CPU cores corresponding to a plurality of service groups, determining the CPU cores corresponding to each service group according to the number of the CPU cores corresponding to each service group, the total number of the CPU cores and the importance level of each service in each service group; wherein, at least one CPU core corresponding to at least one service group is the same as at least one CPU core corresponding to other service groups; and allocating a CPU core corresponding to each service group for each service group.
The device for distributing the central processing unit core provided by the embodiment of the application can execute the technical scheme shown in the embodiment of the method, and the implementation principle and the beneficial effects are similar, and are not repeated here.
In one implementation, the processing module 62 is further configured to: after the CPU core corresponding to each service group is allocated to each service group, the same priority is allocated to each service group; aiming at each service group, when the competing service groups of the service groups exist in the plurality of service groups are identified, adjusting the priority of the service groups or the priority of the competing service groups according to the importance level of each service in the service groups and the importance level of each service in the competing service groups; wherein the at least one CPU core to which the competing service group is assigned is the same as the at least one CPU core to which the service group is assigned.
The device for distributing the central processing unit core provided by the embodiment of the application can execute the technical scheme shown in the embodiment of the method, and the implementation principle and the beneficial effects are similar, and are not repeated here.
In one implementation, the processing module 62 is further configured to: acquiring historical utilization rate of CPU cores corresponding to each service group; for each service group, processing the historical utilization rate of the CPU core corresponding to the service group by utilizing a prediction model to obtain the predicted utilization rate of the CPU core corresponding to the service group; and for each service group, adjusting the number of the CPU cores corresponding to the service group according to the predicted utilization rate of the CPU cores corresponding to the service group.
The device for distributing the central processing unit core provided by the embodiment of the application can execute the technical scheme shown in the embodiment of the method, and the implementation principle and the beneficial effects are similar, and are not repeated here.
In one implementation, the processing module 62 is specifically configured to: and for each service group, when the predicted utilization rate of the CPU cores corresponding to the service group is recognized to exceed a preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the service group, the preset range and the number of the CPU cores corresponding to the service group.
The device for distributing the central processing unit core provided by the embodiment of the application can execute the technical scheme shown in the embodiment of the method, and the implementation principle and the beneficial effects are similar, and are not repeated here.
In one implementation, the predicted utilization of the CPU cores corresponding to the service group includes predicted utilization of the CPU cores corresponding to the service group for a plurality of time periods; the processing module 62 is specifically configured to: for each service group, determining the predicted utilization rate of the CPU core corresponding to the target time period according to the predicted utilization rates of the CPU cores of the plurality of time periods corresponding to the service group; the target time period is a time period acquired in advance; when the predicted utilization rate of the CPU cores corresponding to the target time period is recognized to exceed the preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the target time period, the preset range and the number of the CPU cores corresponding to the service group.
The device for distributing the central processing unit core provided by the embodiment of the application can execute the technical scheme shown in the embodiment of the method, and the implementation principle and the beneficial effects are similar, and are not repeated here.
In one implementation, the processing module 62 is further configured to: for each service group, after the number of CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the service group, judging whether a competing service group of the service groups exists in the service groups or not; when the competing service groups of the service groups exist in the plurality of service groups, the priority of the service groups or the priority of the competing service groups is adjusted according to the importance level of each service in the service groups and the importance level of each service in the competing service groups.
The device for distributing the central processing unit core provided by the embodiment of the application can execute the technical scheme shown in the embodiment of the method, and the implementation principle and the beneficial effects are similar, and are not repeated here.
Fig. 7 is a schematic structural diagram of a server according to an embodiment of the present application. As shown in fig. 7, the server 70 includes: a processor 71 and a memory 72; wherein the processor 71 is communicatively coupled to a memory 72, the memory 72 for storing computer-executable instructions; the processor 71 is configured to execute the technical solutions of any of the method embodiments described above via computer-executable instructions stored in the execution memory 72.
Alternatively, the memory 72 may be separate or integrated with the processor 71. Alternatively, when the memory 72 is a device separate from the processor 71, the server 70 may further include: and a bus for connecting the devices.
The server is used for executing the technical scheme in any of the method embodiments, and the implementation principle and the technical effect are similar, and are not repeated here.
The embodiment of the application also provides a computer readable storage medium, wherein computer executable instructions are stored in the computer readable storage medium, and the computer executable instructions are used for realizing the technical scheme provided by any one of the method embodiments when being executed by a processor.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features can be replaced equivalently; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims (11)

1. A method of allocating a central processor core, comprising:
acquiring a scene type of each service and/or an importance level of each service in response to the allocation request;
dividing a plurality of services into a plurality of service groups according to the scene type of each service and/or the importance level of each service;
at least one central processing unit CPU core is allocated for each service group.
2. The method of allocating CPU cores according to claim 1, wherein said allocating at least one CPU core for each service group comprises:
for each service group, determining the number of CPU cores corresponding to the service group according to the importance level of each service in the service group and the number of the services in the service group;
and distributing at least one CPU core to each service group according to the number of the CPU cores corresponding to each service group.
3. The method for allocating CPU cores according to claim 2, wherein the allocating at least one CPU core for each service group according to the number of CPU cores corresponding to each service group comprises:
acquiring the total number of CPU cores;
According to the number of the CPU cores corresponding to each service group, calculating the total number of the CPU cores corresponding to a plurality of service groups;
under the condition that the total number of CPU cores is identified to be smaller than the total number of CPU cores corresponding to the plurality of service groups, determining the CPU cores corresponding to each service group according to the number of the CPU cores corresponding to each service group, the total number of the CPU cores and the importance level of each service in each service group; wherein, at least one CPU core corresponding to at least one service group is the same as at least one CPU core corresponding to other service groups;
and distributing the CPU cores corresponding to each service group for each service group.
4. The method of allocating a central processor core according to claim 3, further comprising:
after the CPU core corresponding to each service group is allocated to each service group, the same priority is allocated to each service group;
for each service group, when identifying that the competing service group of the service groups exists in the plurality of service groups, adjusting the priority of the service group or the priority of the competing service group according to the importance level of each service in the service group and the importance level of each service in the competing service group; wherein, at least one CPU core allocated to the competing service group is the same as at least one CPU core allocated to the service group.
5. The method of allocating a central processor core according to any of claims 1-4, further comprising:
acquiring historical utilization rate of CPU cores corresponding to each service group;
for each service group, processing the historical use rate of the CPU core corresponding to the service group by utilizing a prediction model to obtain the predicted use rate of the CPU core corresponding to the service group;
and for each service group, adjusting the number of the CPU cores corresponding to the service group according to the predicted utilization rate of the CPU cores corresponding to the service group.
6. The method of allocating a central processor core as in claim 5,
for each service group, according to the predicted utilization rate of the CPU cores corresponding to the service group, the adjusting the number of the CPU cores corresponding to the service group includes:
and for each service group, when the predicted utilization rate of the CPU cores corresponding to the service group is recognized to exceed a preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the service group, the preset range and the number of the CPU cores corresponding to the service group.
7. The method of allocating CPU cores according to claim 6, wherein the predicted usage of CPU cores corresponding to the service group comprises predicted usage of CPU cores for a plurality of time periods corresponding to the service group;
when recognizing that the predicted utilization rate of the CPU cores corresponding to the service group exceeds a preset range for each service group, adjusting the number of the CPU cores corresponding to the service group according to the predicted utilization rate of the CPU cores corresponding to the service group, wherein the preset range and the number of the CPU cores corresponding to the service group comprises:
for each service group, determining the predicted utilization rate of the CPU core corresponding to the target time period according to the predicted utilization rates of the CPU cores of a plurality of time periods corresponding to the service group; the target time period is a time period acquired in advance;
when the predicted utilization rate of the CPU cores corresponding to the target time period is recognized to exceed the preset range, the number of the CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the target time period, the preset range and the number of the CPU cores corresponding to the service group.
8. The method of allocating a central processor core according to claim 5, further comprising:
for each service group, after the number of CPU cores corresponding to the service group is adjusted according to the predicted utilization rate of the CPU cores corresponding to the service group, judging whether a competing service group of the service groups exists in the service groups or not;
and when judging that the competing service groups of the service groups exist in the plurality of service groups, adjusting the priority of the service groups or the priority of the competing service groups according to the importance level of each service in the service groups and the importance level of each service in the competing service groups.
9. An apparatus for distributing cores of a central processing unit, comprising:
the acquisition module is used for responding to the allocation request and acquiring the scene type of each service and/or the importance level of each service;
the processing module is used for dividing the plurality of services into a plurality of service groups according to the scene type of each service and/or the importance level of each service;
the processing module is further configured to allocate at least one central processing unit CPU core for each service group.
10. A server, comprising:
a processor, and a memory communicatively coupled to the processor;
the memory is used for storing computer execution instructions;
the processor is configured to execute the computer-executable instructions stored in the memory to implement the method of allocating a central processor core of any one of claims 1-8.
11. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of allocating a central processor core of any one of claims 1 to 8.
CN202311278554.3A 2023-09-28 2023-09-28 Method, device, server and medium for distributing central processing unit cores Pending CN117331691A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311278554.3A CN117331691A (en) 2023-09-28 2023-09-28 Method, device, server and medium for distributing central processing unit cores

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311278554.3A CN117331691A (en) 2023-09-28 2023-09-28 Method, device, server and medium for distributing central processing unit cores

Publications (1)

Publication Number Publication Date
CN117331691A true CN117331691A (en) 2024-01-02

Family

ID=89278563

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311278554.3A Pending CN117331691A (en) 2023-09-28 2023-09-28 Method, device, server and medium for distributing central processing unit cores

Country Status (1)

Country Link
CN (1) CN117331691A (en)

Similar Documents

Publication Publication Date Title
CN109936604B (en) Resource scheduling method, device and system
US10719343B2 (en) Optimizing virtual machines placement in cloud computing environments
CN107066332B (en) Distributed system and scheduling method and scheduling device thereof
JP6157869B2 (en) Long-term resource provisioning through cascade allocation
US10805385B2 (en) Method and apparatus for managing resource on cloud platform
CN107301093B (en) Method and device for managing resources
EP2725862A1 (en) Resource allocation method and resource management platform
CN109564528B (en) System and method for computing resource allocation in distributed computing
CN112269641B (en) Scheduling method, scheduling device, electronic equipment and storage medium
US11496413B2 (en) Allocating cloud computing resources in a cloud computing environment based on user predictability
US9792142B2 (en) Information processing device and resource allocation method
US10305974B2 (en) Ranking system
CN112988390A (en) Calculation power resource allocation method and device
US20190280945A1 (en) Method and apparatus for determining primary scheduler from cloud computing system
US10606650B2 (en) Methods and nodes for scheduling data processing
CN111258746A (en) Resource allocation method and service equipment
CN112783659A (en) Resource allocation method and device, computer equipment and storage medium
CN110677459A (en) Resource adjusting method and device, computer equipment and computer storage medium
CN115334084A (en) Cloud platform based on cloud computing and internet
CN111338785A (en) Resource scheduling method and device, electronic equipment and storage medium
CN111638953B (en) Method, device and storage medium for realizing GPU virtualization
CN113672345A (en) IO prediction-based cloud virtualization engine distributed resource scheduling method
CN107203256B (en) Energy-saving distribution method and device under network function virtualization scene
CN106325997B (en) Virtual resource allocation method and device
CN117331691A (en) Method, device, server and medium for distributing central processing unit cores

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination