#memory optimization

What is RAM and Why Does It Matter? Random Access Memory (RAM) is your computer’s short-term memory. When you open a program, copy a file, or even just browse the web, data needs somewhere to be stored temporarily while it’s being accessed. RAM provides this space, allowing your computer to quickly retrieve and process information. Insufficient RAM can lead to sluggish performance, frequent…

Kubernetes Streaming: Real-Time Data Pipelines Unlock real-time insights with Kubernetes Streaming! Stream data directly from your applications, enabling instant analytics and faster decision-making. Optimize workflows and gain a competitive edge – explore the power of live data streams today. The introduction of Kubernetes v1.33 marks a significant advancement in how the API server handles…

WinUtilities Pro For Optimizing Your System

WinUtilities Pro Edition is an award-winning collection of tools to optimize and speedup your system performance. This suite contains utilities to clean registry, temporary files on your disks, erase your application and internet browser history, cache, and cookies. It also supports to defragment your disk drives and registry to improve your system performance and stability.

Built-in Startup…

The RAMDisk is easy to use and a reliable piece of the memory optimization software that takes a portion of your system memory and uses it as a disk drive. It is able to speed up applications such as games, Internet Explorer cache for faster web surfing, audio or video editors, CAD programs, databases, and software compilers.

The more RAM your Windows computer has, the larger the RAM Disk you can…

HDFS (Hadoop Distributed File System) çok sayıda küçük dosya ile pek verimli çalışmaz.  HDFS, büyük boyutlu dosyalar üzerinde işlemler gerçekleştirmek için tasarlanmıştır.  Bunun en önemli nedeni, dosyalar erişim için gerekli olan meta verinin Namenode üzerinde dinamik olarak saklanıyor olmasıdır. Çok fazla sayıda küçük dosya bu meta verinin efektif yönetimini zorlaştırır. Hatta bu amaçla konumlandırılan ikincil namenode her ne kadar failover durumları için düşünülse de, belirli periyodlarda asıl namenode hafızasını optimize etmek amaçlı “check pointler” oluşturmak için de kullanılır. HDSF son versiyonunda eklemelere (updates) izin verilmesine rağmen HDFS yapısı, “bir kere yazılıp defalarca oku “ (write one, read all ) prensibine göre çalışır. Hadoop mimarisi master-slave yaklaşımı ile düzenlenmiştir. Namenode master node, slave node ise verilerin saklandığı DataNode’ lardır. HDFS default block size 64 MB’ dır. Daha büyük block size seçilmesi arama kaynaklı gecikmeleri (seek overhead-disk) disk transfer zamanının %1’ i kadar azaltır. Blok boyutu 64 MB dan küçük olan dosyalar HDFS bloğunun tamamını doldurmazlar. Master node hafızası yönettiği slave node ve disk boyutuna göre seçilmelidir. Örneğin 100 makine toplamda 4 TB disk ile replikasyon faktörün 3 olduğu ve 64 MB blok boyutlu seçilen bir durum için :

100x 4 x 1024 x1024 / (3 x64) yaklaşık 2 Milyon MB için 2 GB hafıza seçilmelidir. (her bir milyon MB için 1 GB önerilmektedir)

I recently build a rather large project using Arduino and found myself running out of program space... not SRAM, didnt have any sporadic restarts or "hangs" or glitchy behavior,

just a message saying :

" 33912 bytes (of a 28672 byte maximum) , sketch too big "

I didn't see that coming at all.. mostly because i was doing 2 separate parts of the application and testing them separately, I then combined them and this happened... so here are a few things one can do if you run out of space in Arduino.

don't use floating point math if you don't need to, avoid datatypes like "double" and "float" - in arduino they are the same thing...

The reason is that the Atmega 8 microcontroller does not have a floating point unit... so it is all implemented in software libraries, eating about 2 kbytes of program memory ( FLASH ). So I removed any floating point operations I Had and cleaned up some "if - else" statement and recompiled...

" 31930 bytes (of a 28672 byte maximum) sketch too big "

that's just over 2K of memory, but still too large.. another thing one can do is to tidy up your code, look for places where you do things that are redundant redundant like having multiple "Serial.print("some text"); statements where 1 would be fine. this is a silly example: 

  switch(inputValue)   {   case '1' :     Serial.println("The value was 1");     break;   case '2' :     Serial.println("The value was 2");     break;     case '3' :     Serial.println("The value was 3");     break;     default:       break;   } Can be Replaced by something like :

Serial.print("The value was "); Serial.print(inputValue);

this was a silly example, but its the most simplified way of seeing the error that one can make and how often one has a lot of redundant code... which adds up  eventually. I'll do more posts about memory optimisations like :

using the correct data types ( even in the arduino core files )

avoid too many global variables

removing unused code / things stored in memory that aren't used

removing data that is initialised to a value just be changed again

using C Macros

direct port manipulations

using "inline and "static" functions

smaller buffers for things ( if you know how much data you expect from an SPI or I2C device)

pointers ( this goes with data structures )