Jvm working memory and main memory

in working memory, there are method stack frames and registers. Pc, is understandable, but why should some referenced main memory variables be copied to working memory? I don"t think it"s necessary at all, which leads to cache consistency problems. Or is there a big price to pay for reading and writing main memory that I don"t know? (isn"t the working memory and the main village all in the physical memory? the access speed is not much different in theory, is it because of the price of lock? Or the competition for the bus? )

find all kinds of great solutions%

Java jvm memory concurrent

Mar.09,2021

there are two main types of variables that are copied from main memory to working memory. One explicitly defines local variables, such as XXX foo = this.bar; within the method, and the other is in multicore or multi-CPU systems where data in main memory is read into different caches.

the former actually only affects the reference type, while the latter affects the consistency of all read variables.

Previous: Error starting service with ng-zorro-antd source code! Help!

Next: Gps positioning will have a deviation of 5-10 meters. Now, by comparison, the nearby highway data are located to the corresponding highway location.

MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-1b32e6d-2be46.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-1b32e6d-2be46.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?