HN user

lincpa

32 karma

https://github.com/linpengcheng

Posts5
Comments133
View on HN

Apple M1 unified memory architecture(published on November 11, 2020.) is my "warehouse/workshop model"(hardware architecture section published on February 06, 2019), It is an architecture supported by mathematical models, unlike "von Neumann architecture".

Why my "warehouse/workshop model" can achieve high performance and low power consumption (take Apple M1 chip, Intel AVX-512, Qualcomm as examples)

https://github.com/linpengcheng/PurefunctionPipelineDataflow...

The Math-based Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model

https://github.com/linpengcheng/PurefunctionPipelineDataflow

Its mathematical prototype is the simple, classic, vivid, and widely used in social production practice, elementary school mathematics "water input/output of the pool". My theory rebuilt the theoretical foundation of the IT industry, It makes the computer theory system fully & perfectly related to mathematics in a simple and unified way: from hardware integrated circuits and computer architecture, to software programming methodology, architecture, programming language and so on. It solve the most fundamental and core major problems in the IT industry: The foundation and core of the IT theory lack mathematical support.

My "Warehouse/Workshop Model" is a IT architecture based on mathematical prototype that the simple, classic, and widely used in social production practice, elementary school mathematics "water input/output of the pool".

Software and hardware are factories that manufacture data, so they have the same "warehouse/workshop model" and management methods as the manufacturing industry.

the "Warehouse/Workshop Model" will surely replace the "von Neumann architecture" and become the first architecture in the computer field, and it is the first architecture to achieve a unified software and hardware. Because "von Neumann architecture" lacks mathematical model support, it is impossible to prove its scientificity.

It is an epoch-making theoretical achievement in the IT field, it surpasses the "von Neumann architecture", unifies the IT software and hardware theory, and raises it from the manual workshop production theory level to the modern manufacturing industry production theory Level. Although the Apple M1 chip has not yet fully realized its theory, Apple M1 chip has become the fastest chip in the world.

It has a wide range of applications, from SOC to supercomputer, from software to hardware, from stand-alone to network, from application layer to system layer, from single thread to distributed, from general programming to explainable AI, from manufacturing industry to IT industry, from energy to finance, from the missile's "Fire-and-Forget" technology to Boeing aircraft pulse production line technology .

The Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model: https://github.com/linpengcheng/PurefunctionPipelineDataflow

Why my "warehouse/workshop model" can achieve high performance and low power consumption (take Apple M1 chip, Intel AVX-512, Qualcomm as examples) https://github.com/linpengcheng/PurefunctionPipelineDataflow...

My computer hardware architecture design was published on February 06, 2019. One or two years later, the Apple M1 chip adopted the "warehouse/workshop model" design and was released on November 11, 2020.

Warehouse: unified memory Workshop: CPU, GPU and other cores Products (raw materials): information, data there's also a new unified memory architecture that lets the CPU, GPU, and other cores exchange information between one another, and with unified memory, the CPU and GPU can access memory simultaneously rather than copying data between one area and another. Accessing the same pool of memory without the need for copying speeds up information exchange for faster overall performance. reference: Developer Delves Into Reasons Why Apple's M1 Chip is So Fast

From the introduction Apple M1 has not done global optimization of various core (workshop) scheduling. Apple M1 only optimizes the access to memory data (materials and products in the warehouse). Apple needs to further improve the programming language and compiler to support and promote my programming methodology. My architecture supports a wider range of workshop types than Apple M1, with greater efficiency, scalability and flexibility. Conclusion Apple M1 chip still needs a lot of optimization work, now its optimization level is still very simple, after all, it is only the first generation of works, released in stages. Forecast(2021-01-19): I think Intel, AMD, ARM, supercomputer, etc. will adopt the "warehouse/workshop model"

In the past, the performance of the CPU played a decisive role in the performance of the computer. There were few CPU cores and the number and types of peripherals. Therefore, the CPU became the center of the computer hardware architecture.

Now, with more and more CPU and GPU cores, and the number and types of peripherals, the communication, coordination, and management of cores (or components, peripherals) have become more and more important, They become a key factor in computer performance.

The core views of management science and computer science are the same: Use all available resources to complete the goal with the highest efficiency. It is the best field of management science to accomplish production goals through communication, coordination, and management of various available resources. The most effective, reliable, and absolutely mainstream way is the "warehouse/workshop model".

Only changing the architecture, not changing or only expanding the CPU instruction set, not only will not affect the CPU compatibility, but also bring huge optimization space.

So I think Intel, AMD, ARM, supercomputing, etc. will adopt the "warehouse/workshop model", which is an inevitable trend in the development of computer hardware.

Finally, "Warehouse/Workshop Model" and "Von Neumann Architecture" will become the two major architectures in the IT field.

https://github.com/linpengcheng/PurefunctionPipelineDataflow...

Apple M1 chip adopts Warehouse/Workshop Model

- Warehouse: unified memory

- Workshop: CPU, GPU and other cores

- Product( material): information,data

there’s also a new unified memory architecture that lets the CPU, GPU, and other cores exchange information between one another, and with unified memory, the CPU and GPU can access memory simultaneously rather than copying data between one area and another. Accessing the same pool of memory without the need for copying speeds up information exchange for faster overall performance.

reference:

1. Developer Delves Into Reasons Why Apple’s M1 Chip is So Fast. https://www.macrumors.com/2020/11/30/m1-chip-speed-explanati...

2. The Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Warehouse/Workshop Model https://github.com/linpengcheng/PurefunctionPipelineDataflow

Keep code Simple and Unified.

Keep data and logic separate, data-driven development.

Adhere to the "standardized data interface specification" and use pipeline-functions to manipulate data from the initial state to the final state.

Pipeline-functions conforming to standardized data interfaces are easy to change, replace, and insert extensions.

In the web model, It can be easily replaced as long as the components that conform to the http data specification. For example, Clojure web application model:

- product standard (data interface): the req-map and resp-map of the ring

- warehouse: the ring

- workshop: the pipe functions on both sides of the C/S, and Raw materials (hash-map) are transferred to each other through warehouses through interactions.

https://github.com/linpengcheng/PurefunctionPipelineDataflow

Yes, I never use classes, only data and pipes.

[The Pure Function Pipeline Data Flow v3.0 with Warehouse / Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow)

1. Perfectly defeat other messy and complex software engineering methodologies in a simple and unified way.

2. Realize the unification of software and hardware on the logical model.

3. Achieve a leap in software production theory from the era of manual workshops to the era of standardized production in large industries.

4. It's the basics and the only way to `Software Design/Develop Automation (SDA)`, SDA is an innovative and revolutionary approach to develop large-scale software, just like `Electronic Design Automation (EDA)`, because it systematically simulates an integrated circuit system.

Correct use of functional programming:

[The Pure Function Pipeline Data Flow v3.0 with Warehouse / Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow)

1. Perfectly defeat other messy and complex software engineering methodologies in a simple and unified way.

2. Realize the unification of software and hardware on the logical model.

3. Achieve a leap in software production theory from the era of manual workshops to the era of standardized production in large industries.

4. The basics and the only way to `Software Design Automation (SDA)`, just like `Electronic Design Automation (EDA)`.Because [The Pure Function Pipeline Data Flow] systematically simulates integrated circuit systems.

Industrial-grade Data-Oriented Architecture:

[The Pure Function Pipeline Data Flow v3.0 with Warehouse / Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow)

1. Perfectly defeat other messy and complex software engineering methodologies in a simple and unified way.

2. Realize the unification of software and hardware on the logical model.

3. Achieve a leap in software production theory from the era of manual workshops to the era of standardized production in large industries.

4. The basics and the only way to `Software Design Automation (SDA)`, just like `Electronic Design Automation (EDA)`.

In fact, when you comment, my github adds 5 stars, this shows that my information is valuable. and I have all posted comments on related topics.

I think you should enhance your ability to appreciate technology, Too poor technology should learn more, instead of criticizing others.

Clojure is simpler than Common Lisp, but I still feel that the features are too many and too complicated, and continue to simplify, do not use some complex features, and insist on writing systems with pure pipeline structure.

As a result, the simplest system is obtained, but the design process is a systematic project.It is difficult to design a complex system into a simple and smooth pipeline system.

Typographical error:

1.hellofuck -> hellofunk

2.Show you github or blog -> Show your github or blog

Finally, you try to downvote my comments, and it doesn't make any sense, you should know that everyone's talent is different, just as your talent doesn't suitable for learning my theory, Or rather, you have no fate with the Tao.

If I give an example of one aspect of a topic and students cannot understand other aspects, then I will not repeat the explanation or example.

        ---- Confucius, a famous Chinese educator
    
Imagination is more important than knowledge.

The true sign of intelligence is not knowledge but imagination.

Logic will get you from A to B, imagination will take you everywhere.

        ---- Albert Einstein    
Confucius and Albert Einstein mean the same thing. I have enough examples. If you still do n’t understand, you are not suitable for learning my theory.

My github is mainly my blog and my project homepage, and other code bases are just collections of other excellent developer projects.

I think hellofuck is not good, but he is not convinced, so I think he can show himself with blog or github.

You are too complicated.

```

Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it.

      ---- Alan Perlis, Epigrams in Programming.

           the first recipient of the Turing Award (1966)

           A founding father of Computer Science as a separate discipline           
When the solution is simple, God is answering.

Everything should be as simple as possible, but not simpler.

Most of the fundamental ideas of science are essentially simple, and may, as a rule, be expressed in a language comprehensible to everyone.

If you can't explain it simply, you don't understand it well enough.

Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction.

      ---- Albert Einstein
```

I noticed that you have not posted any useful technical comments in the last 100+ days. Sorry I didn't keep reading.

In fact, this theory has been unprecedentedly hot recently. Star and traffic on github have risen sharply. On 2020-02-27, it was published by editor on reddit/devopsish, and other clojure communities.

My theory is written for a few people who understand Chapter 2 of the "Code Complete" and can read it without reading other chapters, not for people who cannot understand Chapter 2 and focus on other chapters.

So I have stated in the article: I will not write too many application examples or patterns. Because people who like to read such articles can't learn my theory.Because they lack imagination.

```

Imagination is more important than knowledge.

The true sign of intelligence is not knowledge but imagination.

Logic will get you from A to B, imagination will take you everywhere.

        ---- Albert Einstein
```

Programming is like an exam. Good students know where errors might occur after they write code. Bad students do not know whether they are right or wrong and where they are wrong. Therefore, a variety of complex and lengthy error checking systems, such as static type systems. But this is a costly effort with little effect.

Everything is RMDB

I advocate: Building a relational data model on top of hash-map to achieve a combination of NoSQL and RMDB advantages. This is actually a reverse implementation of PostgreSQL.

[Clojure is a functional programming language based on relational database theory](https://github.com/linpengcheng/PurefunctionPipelineDataflow...)

[Everything is RMDB](https://github.com/linpengcheng/PurefunctionPipelineDataflow...)

[Implement relational data model and programming based on hash-map (NoSQL)](https://github.com/linpengcheng/PurefunctionPipelineDataflow...)

modify:

Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it.

      ---- Alan Perlis, Epigrams in Programming.

           the first recipient of the Turing Award (1966)

           A founding father of Computer Science as a separate discipline
           
When the solution is simple, God is answering.

Everything should be as simple as possible, but not simpler.

Most of the fundamental ideas of science are essentially simple, and may, as a rule, be expressed in a language comprehensible to everyone.

If you can't explain it simply, you don't understand it well enough.

Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction.

      ---- Albert Einstein

           The greatest folk scientist in history :-)

           A professional clerk in the patent office
 
           An amateur physicist