In English (origin)
In Russian (translation)
PhD about Erlang memory: "Efficient Memory Management for Message-Passing Concurrency - part I: Single-threaded execution"
Показаны сообщения с ярлыком memory. Показать все сообщения
Показаны сообщения с ярлыком memory. Показать все сообщения
пятница, 27 мая 2011 г.
понедельник, 19 апреля 2010 г.
The Memory Management Glossary
http://www.memorymanagement.org/glossary/ - big memory management glossary with something about 400 terms.
Glossary articles contains links to The Memory Management Reference Full Bibliography.
Bibliography contains many "strange" articles like this "NREVERSAL of Fortune -- The Thermodynamics of Garbage Collection" [PDF].
Glossary articles contains links to The Memory Management Reference Full Bibliography.
Bibliography contains many "strange" articles like this "NREVERSAL of Fortune -- The Thermodynamics of Garbage Collection" [PDF].
пятница, 11 декабря 2009 г.
Jon Masamitsu about TLAB
TLAB == Thread Local Allocation Buffers.
В блоге Jon Masamitsu рассказано как HotSpot 5/6 работает с TLAB.
Также как ими можно управлять/мониторить:
-XX:UseTLAB
-XX:TLABSize
-XX:ResizeTLAB
-XX:MinTLABSize
-XX:+PrintTLAB
В блоге Jon Masamitsu рассказано как HotSpot 5/6 работает с TLAB.
Также как ими можно управлять/мониторить:
-XX:UseTLAB
-XX:TLABSize
-XX:ResizeTLAB
-XX:MinTLABSize
-XX:+PrintTLAB
NUMA, Solaris and memory allocation
Help for the NUMA Weary - Solaris старается выделять память "поближе" к процессору.
пятница, 23 октября 2009 г.
Link: What Every Programmer Should Know About Memory (114 pages)
В ссылке на PDF из поста JAOO: The Concurrency Revolution: The Hardware Story в конце документа Brian Goetz рекомендует два источника.
Вот ссылка на один из них - What Every Programmer Should Know About Memory (114 pages).
Abstract
As CPU cores become both faster and more numerous, the limiting factor for most programs is now, and will be for some time, memory access. Hardware designers have come up with ever more sophisticated memory handling and acceleration techniques–such as CPU caches–but these cannot work optimally without some help from the programmer. Unfortunately, neither the structure nor the cost of using the memory subsystem of a computer or the caches on CPUs is well understood by most programmers. This paper explains the structure of memory subsystems in use on modern commodity hardware, illustrating why CPU caches were developed, how they work, and what programs should do to achieve optimal performance by utilizing them.
Вот ссылка на один из них - What Every Programmer Should Know About Memory (114 pages).
Abstract
As CPU cores become both faster and more numerous, the limiting factor for most programs is now, and will be for some time, memory access. Hardware designers have come up with ever more sophisticated memory handling and acceleration techniques–such as CPU caches–but these cannot work optimally without some help from the programmer. Unfortunately, neither the structure nor the cost of using the memory subsystem of a computer or the caches on CPUs is well understood by most programmers. This paper explains the structure of memory subsystems in use on modern commodity hardware, illustrating why CPU caches were developed, how they work, and what programs should do to achieve optimal performance by utilizing them.
Подписаться на:
Сообщения (Atom)