HTTP Changes

Posted on by lechuck park

From Claude with some prompting
HTTP: HTTP uses text-based HTML with a head and body structure. HTTP/1.1 introduced Keep-Alive for maintaining TCP connections, but suffers from header overhead and Head-of-Line Blocking issues. Servers cannot push data without a client request.

HTTP/2: HTTP/2 introduced binary framing to improve performance. It enhances efficiency through header compression and multiplexing, and added server push functionality. It also strengthened authentication and encryption using TLS/SSL.

HTTP/3: HTTP/3 operates over the QUIC protocol using UDP instead of TCP. It includes TLS 1.3 by default and provides lower latency and improved multiplexing. HTTP/3 significantly enhances performance through 0-RTT connection establishment, elimination of TCP handshakes, and solving Head-of-Line Blocking issues. It also offers reliable data streams over UDP and ensures data ordering on each stream.

RISC-V

Posted on by lechuck park

From Claude with some prompting
This image summarizes the key features of the RISC-V architecture:

  1. Open Source: Described as “Everybody Can Use.”
  2. Modularity: Supports “Light Embedded ~ High Computing” applications.
  3. Scalability: Supports “32-bit, 64-bit, and 128-bit address spaces.”
  4. Extension Modules: Includes “floating-point operations, vector operations ++”
  5. Widespread Adoption: “Wide Use chip design, hardware accelerators ++”

The bottom of the image states: “More Better For Specific ML works (Not all replacement of GPU)”

Overall, this image highlights RISC-V’s flexibility, scalability, and applicability in various computing environments. It emphasizes RISC-V’s potential in certain machine learning tasks, while noting that it’s not a complete replacement for GPUs in all ML applications. The architecture is presented as adaptable, from lightweight embedded systems to high-performance computing, with wide-ranging adoption in chip design and hardware acceleration.

Real

Posted on by lechuck park

From Claude with some prompting
This diagram illustrates the process of human understanding of reality, highlighting the potential discrepancy between “Real Existence” and “Human Real”. The flow chart demonstrates:

  1. REAL EXISTENCE: Represents the objective reality, including the universe and all its phenomena.
  2. Energy Movement: Symbolizes the physical processes occurring in reality.
  3. Sensing: The stage where human sensory organs collect information, albeit in a limited capacity.
  4. Observation: Involves “Sampling”, indicating that we only perceive and process a fraction of reality.
  5. Human Knowledge: Represents the subjective understanding formed based on observed information.

This process underscores a crucial philosophical and epistemological issue: the gap between objective reality and human perception of reality. Humans are constrained by their sensory capabilities and observational methods, leading to a potentially incomplete or distorted understanding of the true nature of existence.

The diagram implies that what we consider “real” may differ significantly from absolute reality due to the limitations of human perception and cognition. This concept is fundamental in various fields, including philosophy, science, and epistemology, challenging our assumptions about knowledge and truth.

This perspective emphasizes the inherent limitations of human understanding and suggests that our perception of reality is inevitably filtered and potentially biased by our cognitive processes and sensory limitations.

HTTP Service components

Posted on by lechuck park

From Claude with some prompting
This image illustrates the network structure of an HTTP service. The main components are:

Client Side:

  • Browser: Handles URL requests, HTML parsing, and JavaScript execution
  • OS: Runs the browser, translates URL (domain) to IP

Internet:

  • DNS: Converts domain names to IP addresses
  • IP: Transfers data using IP addresses

Server Side:

  • OS (Operating System): Runs applications, manages IP network
  • TLS: Handles encryption
  • WEB:
    • Manages HTML embedding
    • Handles JSP (JavaServer Pages)
    • Typically deals with static content and some dynamic content generation
  • WAS (Web Application Server):
    • Handles server-side programming and application logic
    • Manages complex dynamic content generation
    • Interacts with the database
    • Handles business logic of the application
  • DB: Database for storing and retrieving data for web services

The diagram shows the entire process of how an HTTP request is handled, from the web browser to the server’s database. It briefly explains the technologies and protocols involved at each step, providing a helpful overview of the basic structure of web services.

Optimization 2

Posted on by lechuck park

From Claude with some prompting
This image titled “Optimization II” illustrates the process of optimization between Supply and Usage. Here’s a comprehensive interpretation:

  1. The top shows a simple diagram depicting the basic relationship between Supply and Usage.
  2. The middle section presents graphs showing the fluctuations of Supply and Usage over time, comparing the states before and after optimization.
  3. The equation “Supply – Usage = Optimization Target” is provided, clearly defining the optimization goal.
  4. The bottom diagram illustrates the optimization process. It shows that optimization continues until the ‘Optimization Target Cost’ is less than the ‘Supply – Usage Cost’. This is to ensure that the cost of optimization doesn’t exceed the cost difference between supply and usage.
  5. The right-side graphs and explanation demonstrate that as the rate of change in usage increases (with high and low frequency), the need for optimization work becomes greater.
  6. The question “By What? By Manual? Software system?” is posed, prompting consideration of how to address this increased need for optimization – whether through manual processes or software systems.

Overall, this diagram emphasizes the importance of the optimization process between supply and usage, the efficiency of optimization costs, the increased need for optimization as usage patterns change, and the necessity to consider practical solutions for implementing these optimizations.