SOLUTIONS / VDS
When looking for a VDS, focus on how the application uses resources rather than the package label. Review CPU sharing, memory, storage and operations together when comparing FibaCloud server options. Distinguish a virtual server requirement from a need to control an entire physical machine.
01 / Overview
VDS and VPS can describe different packages at different providers; neither label creates a standard performance or isolation guarantee. Base selection on actual CPU allocation, memory, storage conditions and service scope.
Assess Dedicated CPU for sustained processing, and Bare Metal when physical hardware control is required. Virtualization, resource allocation and operating management are separate questions. A package called dedicated does not imply that every layer belongs exclusively to you.
Distinguish sustained processing from brief bursts. Measure single-thread and multi-thread behaviour when evaluating CPU allocation.
Working sets and concurrent processes determine memory needs. Dedicated CPU does not automatically fix insufficient memory or inefficient queries.
Separate virtual machine management from physical server management. Check operating system, licensing and specialist software requirements before selection.
02 / Architecture
Conceptual comparison: CPU allocation and control of a physical server are different decisions. Actual scope depends on the selected product terms.
Selection guide03 / Selection guide
| Consider | How to decide | Why it matters |
|---|---|---|
| Resource model | Verify CPU sharing and allocation terms in the relevant product. | VDS and VPS labels do not replace technical scope. |
| Application behaviour | Measure latency, job duration and utilization with representative data. | Selection does not depend on core count alone. |
| Control requirements | Determine whether a virtual or physical machine is needed. | The distinction between Dedicated CPU and Bare Metal becomes clear. |
| Data and operations | Assign backups, updates and resource-change responsibilities. | Dedicated resources still require ongoing maintenance. |
04 / Use cases
Measure representative busy periods for APIs and workers. Observe CPU, memory and data access together.
Assess job duration, concurrency and temporary storage. More vCPUs do not imply proportional acceleration for every task.
Measure memory, query and disk behaviour. Plan database software and application ownership alongside infrastructure.
Plans & pricing
| Package | CPU | RAM | Storage | Bandwidth | Monthly price (USD) |
|---|---|---|---|---|---|
|
Shared 1
|
1 CPU
|
1 GB
|
25 GB
|
2TB
|
4.00$Hourly: 0,005
|
|
Shared 2
|
1 CPU
|
2 GB
|
50 GB
|
3TB
|
6.00$Hourly: 0,008
|
|
Shared 3
|
2 CPU
|
4 GB
|
80 GB
|
5TB
|
12.00$Hourly: 0,016
|
|
Shared 4
|
4 CPU
|
8 GB
|
160 GB
|
6TB
|
24.00$Hourly: 0,032
|
|
Shared 5
|
6 CPU
|
16 GB
|
320 GB
|
10TB
|
49.00$Hourly: 0,068
|
|
Shared 6
|
8 CPU
|
32 GB
|
640 GB
|
20TB
|
94.00$Hourly: 0,130
|
|
Shared 7
|
16 CPU
|
64 GB
|
1280 GB
|
22TB
|
180.00$Hourly: 0,250
|
|
Shared 8
|
32 CPU
|
128 GB
|
2560 GB
|
25TB
|
360.00$Hourly: 0,500
|
| Package | CPU | RAM | Storage | Bandwidth | Monthly price (USD) |
|---|---|---|---|---|---|
|
Dedicated 1
|
2 CPU
|
4 GB
|
80 GB
|
6TB
|
16.00$Hourly: 0,022
|
|
Dedicated 2
|
4 CPU
|
8 GB
|
160 GB
|
7TB
|
28.00$Hourly: 0,038
|
|
Dedicated 3
|
8 CPU
|
16 GB
|
320 GB
|
8TB
|
49.00$Hourly: 0,068
|
|
Dedicated 4
|
16 CPU
|
32 GB
|
640 GB
|
9TB
|
94.00$Hourly: 0,130
|
|
Dedicated 5
|
32 CPU
|
64 GB
|
1280 GB
|
12TB
|
180.00$Hourly: 0,250
|
|
Dedicated 6
|
48 CPU
|
96 GB
|
1920 GB
|
14TB
|
260.00$Hourly: 0,361
|
|
Dedicated 7
|
50 CPU
|
128 GB
|
2500 GB
|
16TB
|
340.00$Hourly: 0,472
|
|
Dedicated 8
|
56 CPU
|
256 GB
|
5000 GB
|
18TB
|
490.00$Hourly: 0,680
|
| Package | CPU | RAM | Storage | Bandwidth | Monthly price (USD) |
|---|---|---|---|---|---|
|
High Memory 1
|
2 CPU
|
24 GB
|
20 GB
|
6TB
|
28.00$Hourly: 0,038
|
|
High Memory 2
|
4 CPU
|
48 GB
|
40 GB
|
8TB
|
49.00$Hourly: 0,068
|
|
High Memory 3
|
6 CPU
|
90 GB
|
90 GB
|
10TB
|
74.00$Hourly: 0,102
|
|
High Memory 4
|
10 CPU
|
150 GB
|
200 GB
|
12TB
|
120.00$Hourly: 0,166
|
Review the current configuration, price and order terms before selecting a service.
Choose a location to measure your connection latency.
05 / From planning to operation
List CPU, memory, storage and software needs. State the required level of control separately.
Review Shared CPU, Dedicated CPU and Bare Metal scope. Compare pricing and resources against the same requirement.
Use the same data and operations for candidate configurations. Record warm-up, dependencies and test conditions.
Complete access, updates and recovery procedures. Review resizing conditions together with data protection.
No. Providers may use the labels for different technical arrangements. The resource model and measurements from your application are more useful.
No. CPU allocation differs from exclusive use of a physical machine. Assess Bare Metal separately when that control is required.
No. Single-thread limits, data access or external services can constrain growth. Select resources through workload measurement.
Backups remain necessary. Application mistakes, deletion and corrupt data are independent of resource allocation. Define scope and test recovery.
Connect product decisions with installation, configuration and operating knowledge.
These references explain the technical concepts discussed on this page. Available configurations and service scope are defined by FibaCloud product and order information.
FIBACLOUD / VDS Servers
Tell us about your application, expected usage and operating requirements. Let’s bring the resource choices together.
