{"id":35632,"date":"2023-12-01T05:10:25","date_gmt":"2023-12-01T05:10:25","guid":{"rendered":"https:\/\/accuweb.cloud\/resource\/faq\/what-is-cloudlets\/"},"modified":"2026-02-19T12:21:02","modified_gmt":"2026-02-19T12:21:02","slug":"what-are-cloudlets","status":"publish","type":"faq","link":"https:\/\/accuweb.cloud\/resource\/articles\/what-are-cloudlets","title":{"rendered":"What are Cloudlets?"},"content":{"rendered":"

What are Cloudlets?<\/h2>\n

\"Accuweb.Cloud<\/a><\/p>\n

Cloudlets<\/b> are the fundamental building blocks of the AccuWeb.Cloud platform infrastructure<\/b>. Each Cloudlet represents a small unit of computing power – providing 128 MiB of RAM<\/b> and 200 MHz of CPU<\/b>. This precise allocation helps the platform deliver just the right amount of capacity for every task or application, ensuring optimal performance without wasting resources.<\/p>\n

AccuWeb.Cloud uses containers<\/b> to run applications efficiently. You can think of a container as a small, self-contained box<\/b> that holds each application separately. These containers are designed to share key parts of the computer\u2019s operating system such as the kernel (the system\u2019s brain)<\/b>, TCP\/IP stack (network communication system)<\/b>, and file system (storage)<\/b>.<\/p>\n

By sharing these system components, containers reduce memory usage and CPU load, allowing applications to run faster, smoother, and more efficiently<\/b>. It\u2019s similar to how your smartphone runs multiple apps at once without slowing down smart resource sharing keeps everything running seamlessly.<\/p>\n

\t\t
\n\t\t\t
\n \n
\n
\n
\n \n \t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t<\/div>\n
<\/div>\n

Understanding Cloudlets<\/h3>\n

Cloudlets<\/b> are designed to scale effortlessly, expanding or shrinking as your application\u2019s needs change. If your app suddenly requires more power, Cloudlets can instantly provide it, just like adjusting the size of a container to give your application more room to grow.<\/p>\n

\"Vertical<\/a><\/p>\n

Each application runs inside its own container<\/b>, keeping environments completely separate like having individual rooms for different tasks. This isolation ensures that if one application faces an issue, it doesn\u2019t affect others, improving overall stability and performance.<\/p>\n

In short, Cloudlets power applications through efficient, secure, and scalable containers<\/b>. They automatically adjust resources based on demand, maintain separation for reliability, and offer built-in protection to keep your data safe.<\/p>\n

Let’s break it down: What is a Cloudlet in AccuWeb.Cloud ?<\/strong><\/p>\n

\"Cloudlet\"<\/a><\/p>\n

<\/div>\n
1 Cloudlet = 128 MiB of RAM + 200 MHz of CPU power<\/div>\n
<\/div>\n

So Cloudlets act as a way to measure the computing capacity you are using in the cloud. Instead of paying for an entire server, you only pay for your application’s exact resources, measured in Cloudlets.<\/p>\n

There are two main types of Cloudlets<\/h3>\n

Reserved Cloudlets \"reserved<\/h3>\n

These are resources you reserve in advance, regardless of whether you end up using them or not. The more you reserve, the more significant discount you get. It’s like booking your seat at a concert ahead of time.<\/p>\n

\"Scaling<\/a><\/p>\n

Dynamic Cloudlets \"dynamic<\/h3>\n

These resources are automatically added or removed based on your real-time usage. So you only pay for what you end up using, like paying for rides on a trip based on how many you take.<\/p>\n

\"Reserved<\/a><\/p>\n

The benefit of using both Reserved and Dynamic Cloudlets is that you get discounts for reserving Cloudlets in advance but can scale up and down flexibly based on your needs.<\/p>\n

So in everyday terms, you can think of Cloudlets like food units at a buffet. You pay for the amount you take, not the whole buffet. Reserved Cloudlets are like your favorite dishes you know you’ll take. Dynamic Cloudlets are additional items you may take depending on your appetite.<\/p>\n

By using Cloudlets, you only pay for your application’s exact computing resources. No overpaying for unused capacity! So next time you come across the term, remember Cloudlets are simply a way to measure and pay for computing resources as you use them. Pretty simple, right?<\/p>\n

\t\t
\n\t\t\t
\n \n
\n
\n
\n \n \t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t<\/div>\n
<\/div>\n

Understanding Cloudlet Consumption<\/h3>\n

Cloudlet consumption is calculated based on two main factors: RAM (memory) and CPU (processing power)<\/p>\n

\"Cloudlet<\/a><\/p>\n

Let’s break down how it works<\/h3>\n
    \n
  1. RAM Consumption<\/strong>: RAM is the memory your application and processor utilize to store and access data. Cloudlets measure RAM consumption by considering the peak value of RAM usage over an hour. Each cloudlet represents 128 MiB of RAM, approximately 1 GB of memory. For example, if your highest RAM usage during an hour is 1024 MiB, it would equal 8 cloudlets or approximately 1 GB of memory.<\/li>\n
  2. CPU Consumption<\/strong>: The CPU is the brain of your computer or server, responsible for executing instructions and performing calculations. Cloudlets measure CPU consumption by considering the average CPU usage over an hour. Each cloudlet corresponds to 200 MHz of CPU power. For instance, if your average CPU usage is 2400 MHz (12 cloudlets) for an hour, it would be equivalent to 12.<\/li>\n<\/ol>\n

    Cloudlet Consumption Tracking<\/h3>\n

    Cloudlet consumption is calculated on an hourly basis using the following approach:<\/p>\n