跳到主要內容

Install K8S on VM and spring boot integration.

Installation Environment Vmware Workstation pro  It is recommended to use the  snapshot  to store the state of each installation stage to avoid installation failures and causing the installation to start from scratch. Ubuntu 22.04 windows 11 Hardware settings  create 3 VM: 4 cores and 4G memory and 100G capacity Before installing K8s (All use the root user) set host: 192.168.47.135 master 192.168.47.131 node1 192.168.47.132 node2 set root ssh connection: sudo su - echo "PermitRootLogin yes" >> /etc/ssh/sshd_config systemctl restart sshd sudo passwd ssh-keygen for i in {master,node1,node2}; do  ssh-copy-id root@$i; done set Ipvs and conf  create conf file: for i in {master,node1,node2}; do ssh root@$i 'cat << EOF > /etc/modules-load.d/containerd.conf overlay br_netfilter EOF'; done execute conf: for i in {master,node1,node2}; do ssh root@$i 'modprobe overlay;modprobe br_netfilter;'; done create 99-kubernetes-cri.conf file: for i in {maste...
張貼留言

Cpu scheduling

Basic concept

  • The idea of multiprogramming:
    • Keep several processes in memory. Every time one process has to wait, another process takes over the use of the CPU.
  • CPU-I/O burst cycle:
    • Process execution consists of a cycle of CPU execution and I/O wait(i.e., CPU burst and I/O burst).
    • Generally, there is a large number of short CPU bursts and a small number of long CPU bursts
    • An I/O-bound program would typically have many very short CPU bursts.
    • A CPU-bound program might have a few long CPU bursts.

CPU scheduler

Select from the ready queue to execute(I.e allocates an APU for the selected process)
CPU scheduling  decision may take place when a process:
  1. Switch from running to waiting state.
  2. Switch from running to ready state.
  3. Switch from waiting to ready.
  4. Terminates.
  • Non-preemptive scheduling:
    • Scheduling under 1 and 4(no choice in terms of scheduling).
    • The process keeps the CPU until it is terminated or switched to the waiting state.
  • Preemptive scheduling:
    • Scheduling under all cases.

Scheduling Criteria

  • CPU utilization
    • Theoretically: 0% ~100%
    • Real system: 40%(light)~90%(heavy)
  • Throughput
    • Number of completed processes per time unit
  • Turnaround time
    • Submission ~ completion
  • Waiting time
    • Total waiting time in the ready queue
  • Response time
    • Submission ~ the first response is produced

Algorithms

  • First-Come, First-Served(FCFS) scheduling.
  • Shortest-job-First(SJF) scheduling.
    • Approximate shortest-job-first(SJF):
      • SJF-difficulty: no way to know the length of the next CPU burst.
      • Approximate SJF: the next burst can be predicted as an exponential average of the measured length of the previous CPU burst.
  • Priority scheduling.
    • Problem: starvation(low-priority processes never execute).
    • Solution: aging(as time progresses increases the priority of processes.
  • Round-Robin scheduling.
  • Multilevel queue scheduling.
  • Multilevel feedback queue scheduling.

Evaluation methods

  • Deterministic modeling - takes a particular predetermined workload and defines the performance of each algorithm for that workload, cannot be generalized.
  • Queueing model - mathematical analysis.
  • Simulation - random-number generator or trace tapes for workload generation.
  • Implementation - the only completely accurate algorithm evaluation.
reference:
https://www.amazon.com/-/zh_TW/Operating-System-Concepts-Abraham-Silberschatz/dp/1119800366/ref=sr_1_1?keywords=Operating-System-Concepts&qid=1669538704&s=books&sr=1-1


留言

張貼留言

這個網誌中的熱門文章

Install K8S on VM and spring boot integration.

Installation Environment Vmware Workstation pro  It is recommended to use the  snapshot  to store the state of each installation stage to avoid installation failures and causing the installation to start from scratch. Ubuntu 22.04 windows 11 Hardware settings  create 3 VM: 4 cores and 4G memory and 100G capacity Before installing K8s (All use the root user) set host: 192.168.47.135 master 192.168.47.131 node1 192.168.47.132 node2 set root ssh connection: sudo su - echo "PermitRootLogin yes" >> /etc/ssh/sshd_config systemctl restart sshd sudo passwd ssh-keygen for i in {master,node1,node2}; do  ssh-copy-id root@$i; done set Ipvs and conf  create conf file: for i in {master,node1,node2}; do ssh root@$i 'cat << EOF > /etc/modules-load.d/containerd.conf overlay br_netfilter EOF'; done execute conf: for i in {master,node1,node2}; do ssh root@$i 'modprobe overlay;modprobe br_netfilter;'; done create 99-kubernetes-cri.conf file: for i in {maste...
張貼留言
閱讀完整內容

ShardingSphere

Table of contents [ hide ]  ShardingSphere The distributed SQL transaction & query engine for data sharding, scaling, encryption, and more - on any database. ShardingJDBC ShardingSphere-JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. ShardingProxy ShardingSphere-Proxy is a transparent database proxy, providing a database server that encapsulates database binary protocol to support heterogeneous languages. Core Concept 1. Virtual Database Provides a virtual database with sharding capabilities, allowing applications to be easily used as a single database 2. Real Database The database that stores real data in the shardingShereDatasource instance for use by ShardingSphere 3. Logic Table Tables used by the application 4. Real Table In the table that stores real data, the data structure is the same as the logical table. The application maintains the mapping between the logical table and the real table. All real tables map to ShardingS...
張貼留言
閱讀完整內容

Kafka

Table of contents [ hide ] Kafka Apache Kafka is an open-source distributed event streaming platform used by thousands of companies for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications. Why use a Message Queue like Kafka 1. Asynchronous The program can continue execution without waiting for I/O to complete, increasing throughput. 2. Decoupling It refers to reducing the dependencies between different parts of the system so that each component of the system can be developed, maintained, and evolved relatively independently. The main goal of decoupling is to reduce tight coupling between components to improve system flexibility, maintainability, and scalability. 3. Peak clipping Peak clipping is essential to delay user requests more, filter user access needs layer by layer, and follow the principle of "the number of requests that ultimately land on the database is as small as possible". Basic Concept 1. Client Includi...
張貼留言
閱讀完整內容