{"id":965,"date":"2026-08-24T22:37:51","date_gmt":"2026-08-24T22:37:51","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=965"},"modified":"2026-08-24T22:37:51","modified_gmt":"2026-08-24T22:37:51","slug":"mysql-mariadb-performance-tuning-low-ram-vps","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/","title":{"rendered":"MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">MySQL and MariaDB are the most popular database engines for VPS-hosted web applications, but their default configurations are designed for dedicated servers with abundant RAM. On a 1\u20134 GB VPS, the default values for buffer pools, cache sizes, and connection limits can quickly exhaust memory and trigger swapping. This guide provides a data-driven methodology for tuning MySQL\/MariaDB on a RAM-constrained VPS, with specific configuration values for 1 GB, 2 GB, and 4 GB instances.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The Baseline: Why Defaults Are Wrong for a VPS<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A default MySQL installation on Ubuntu 22.04 allocates approximately 600\u2013800 MB of RAM through the InnoDB buffer pool (128 MB), query cache (disabled), temporary tables, and per-connection buffers. This is reasonable for a 4 GB server but dangerously high for a 1 GB VPS where the operating system, web server, and PHP-FPM all share the same memory. When MySQL exceeds available RAM, the kernel swaps, which degrades database performance by orders of magnitude \u2014 a single swap page fault can take 10\u201350 ms compared to 1\u201310 \u00b5s for a RAM access.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The first step is measuring your current memory usage:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Check MySQL memory usage by performance_schema\nSELECT * FROM sys.memory_global_total;\n\n# Or use the process list\nSELECT * FROM information_schema.PROCESSLIST;\n\n# System-wide memory\nfree -h\n# Look at the \"available\" column, not \"free\"<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Key Configuration Parameters<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. InnoDB Buffer Pool Size<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The InnoDB buffer pool is the single largest consumer of memory in MySQL. It caches table data and indexes. The optimal size depends on your working set (the data you access frequently) and available RAM. A common rule of thumb is 50\u201370% of available RAM, but on a VPS this must be reduced to leave room for the OS, web server, and PHP workers.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>VPS RAM<\/th><th>Recommended Buffer Pool<\/th><th>Percentage<\/th><th>Max Working Set<\/th><\/tr><\/thead><tbody><tr><td>1 GB<\/td><td>128\u2013256 MB<\/td><td>12\u201325%<\/td><td>~200 MB<\/td><\/tr><tr><td>2 GB<\/td><td>512\u20131024 MB<\/td><td>25\u201350%<\/td><td>~800 MB<\/td><\/tr><tr><td>4 GB<\/td><td>1536\u20132560 MB<\/td><td>37\u201362%<\/td><td>~2 GB<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Set in <code>my.cnf<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>[mysqld]\n# 1 GB VPS: 256M\n# 2 GB VPS: 768M\n# 4 GB VPS: 2G\ninnodb_buffer_pool_size = 256M<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Monitor buffer pool efficiency after setting:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SHOW ENGINE INNODB STATUS\\G\n# Look for \"Buffer pool hit rate\" - should be above 99%\n# If below 95%, increase the buffer pool size if RAM permits<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">2. Per-Thread Buffers<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Each MySQL connection allocates a set of per-thread buffers. These multiply by the number of concurrent connections, so they must be kept small on a VPS.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>[mysqld]\n# Sort buffer: used for ORDER BY and GROUP BY operations\n# Default: 256K, keep at 256K for small VPS\nsort_buffer_size = 256K\n\n# Join buffer: used for joins that cannot use indexes\n# Default: 256K, keep small\njoin_buffer_size = 256K\n\n# Read buffer: sequential scans\n# Default: 128K\nread_buffer_size = 128K\n\n# Read random buffer: random reads\nread_rnd_buffer_size = 256K\n\n# Temp table: for complex queries creating temporary tables\ntmp_table_size = 32M\nmax_heap_table_size = 32M<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3. Connection Limits<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Each connection consumes RAM. On a VPS with limited memory, cap the maximum connections and reduce the connection timeout to prevent runaway connection accumulation.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>[mysqld]\n# 1 GB VPS: 20-50 connections\n# 2 GB VPS: 50-100 connections\n# 4 GB VPS: 100-200 connections\nmax_connections = 50\n\n# Close idle connections after 60 seconds (default: 28800 = 8 hours!)\nwait_timeout = 60\ninteractive_timeout = 120\n\n# Thread cache: reuse thread structures instead of creating new ones\nthread_cache_size = 8<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Calculate your maximum connection memory consumption:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Approximate memory per connection:\n# sort_buffer (256K) + join_buffer (256K) + read_buffer (128K) + read_rnd_buffer (256K)\n# + thread stack (~256K) + tmp table (up to 32M but only for active queries)\n# = ~1.2 MB per idle connection, up to ~33 MB for active connections with temp tables\n# With 50 connections: ~60 MB idle, ~1.6 GB worst-case with all temp tables<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">4. Log File Size and Flush Method<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The InnoDB redo log size affects write performance and crash recovery time. On a VPS, keep log files small enough for fast recovery but large enough to avoid log contention:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>[mysqld]\n# InnoDB log file size (total = innodb_log_file_size * innodb_log_files_in_group)\n# 1 GB VPS: 128M * 2 = 256M total\n# 2 GB VPS: 256M * 2 = 512M total\n# 4 GB VPS: 512M * 2 = 1G total\ninnodb_log_file_size = 128M\ninnodb_log_files_in_group = 2\n\n# Flush method: O_DIRECT avoids double buffering (page cache + buffer pool)\n# This is recommended for VPS environments\ninnodb_flush_method = O_DIRECT\n\n# Flush log at every transaction commit (safe but slower)\n# For most web applications, this is the right balance\ninnodb_flush_log_at_trx_commit = 1<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5. Query Cache (Disable on Modern MySQL)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The query cache is deprecated in MySQL 5.7 and removed in MySQL 8.0. In MariaDB, it still exists but is typically counterproductive on multi-core VPS because it requires a global mutex that serializes query execution. Disable it:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>[mysqld]\n# MySQL 5.7+ (deprecated)\nquery_cache_type = 0\nquery_cache_size = 0\n\n# MariaDB (still exists)\nquery_cache_type = 0\nquery_cache_size = 0<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Use application-level caching (Redis, Memcached) instead of the query cache for better performance and scalability.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Complete Configuration Templates<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1 GB VPS (e.g., WordPress, small application)<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>[mysqld]\ninnodb_buffer_pool_size = 256M\ninnodb_log_file_size = 128M\ninnodb_flush_method = O_DIRECT\nmax_connections = 50\nwait_timeout = 60\nsort_buffer_size = 256K\njoin_buffer_size = 256K\nread_buffer_size = 128K\nread_rnd_buffer_size = 256K\ntmp_table_size = 32M\nmax_heap_table_size = 32M\nthread_cache_size = 8\nquery_cache_type = 0\nquery_cache_size = 0\ninnodb_flush_log_at_trx_commit = 1<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">2 GB VPS (e.g., WooCommerce, moderate traffic)<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>[mysqld]\ninnodb_buffer_pool_size = 768M\ninnodb_log_file_size = 256M\ninnodb_flush_method = O_DIRECT\nmax_connections = 100\nwait_timeout = 120\nsort_buffer_size = 256K\njoin_buffer_size = 256K\nread_buffer_size = 256K\nread_rnd_buffer_size = 512K\ntmp_table_size = 64M\nmax_heap_table_size = 64M\nthread_cache_size = 16\nquery_cache_type = 0\nquery_cache_size = 0\ninnodb_flush_log_at_trx_commit = 1<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">4 GB VPS (e.g., high-traffic application, multiple sites)<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>[mysqld]\ninnodb_buffer_pool_size = 2G\ninnodb_log_file_size = 512M\ninnodb_flush_method = O_DIRECT\nmax_connections = 200\nwait_timeout = 180\nsort_buffer_size = 512K\njoin_buffer_size = 512K\nread_buffer_size = 256K\nread_rnd_buffer_size = 512K\ntmp_table_size = 128M\nmax_heap_table_size = 128M\nthread_cache_size = 32\nquery_cache_type = 0\nquery_cache_size = 0\ninnodb_flush_log_at_trx_commit = 1<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Monitoring and Tuning After Configuration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After applying the configuration, monitor these metrics to verify the settings are working:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Buffer pool hit rate (should be &gt; 99%)\nSHOW ENGINE INNODB STATUS\\G\n# Look for: \"Buffer pool hit rate 1000 \/ 1000\"\n\n# Current connections vs max\nSHOW VARIABLES LIKE 'max_connections';\nSHOW STATUS LIKE 'Threads_connected';\n\n# Slow queries\nSHOW GLOBAL STATUS LIKE 'Slow_queries';\n\n# Temporary tables created on disk (should be near zero)\nSHOW GLOBAL STATUS LIKE 'Created_tmp_disk_tables';\n\n# Sorting using files (should be minimal)\nSHOW GLOBAL STATUS LIKE 'Sort_merge_passes';<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If <code>Created_tmp_disk_tables<\/code> is high, increase <code>tmp_table_size<\/code> and <code>max_heap_table_size<\/code>. If <code>Sort_merge_passes<\/code> is high, increase <code>sort_buffer_size<\/code>. If the buffer pool hit rate is below 99%, increase <code>innodb_buffer_pool_size<\/code> if RAM allows.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Additional Memory-Saving Techniques<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Use MariaDB instead of MySQL:<\/strong> MariaDB uses significantly less memory for the same workload. On a 1 GB VPS, MariaDB can save 50\u2013100 MB compared to MySQL 8.0.<\/li>\n<li><strong>Disable performance_schema:<\/strong> The performance schema consumes approximately 200 MB of memory on MySQL 8.0. Disable it with <code>performance_schema = OFF<\/code> in <code>my.cnf<\/code> if you do not need detailed instrumentation.<\/li>\n<li><strong>Reduce InnoDB buffer pool instances:<\/strong> Set <code>innodb_buffer_pool_instances<\/code> to 1 for buffer pools under 1 GB. Each instance adds memory overhead for bookkeeping structures.<\/li>\n<li><strong>Enable InnoDB page compression:<\/strong> For tables with compressible data (text, JSON), enable <code>innodb_page_compression<\/code>. This trades CPU for memory, which is a favorable trade-off on a RAM-constrained VPS.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">What to Avoid on a Low-RAM VPS<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Do not set innodb_buffer_pool_size too high:<\/strong> If the buffer pool causes swapping, performance drops catastrophically. Measure your actual hit rate and adjust conservatively.<\/li>\n<li><strong>Do not increase per-thread buffers without monitoring:<\/strong> A single large sort buffer is fine, but multiply it by 50 connections and it becomes 12.5 MB of unnecessary allocation.<\/li>\n<li><strong>Do not enable the query cache on MySQL 8.0:<\/strong> It does not exist. On MariaDB, keep it disabled.<\/li>\n<li><strong>Do not use MyISAM tables:<\/strong> MyISAM uses table-level locking and is not crash-safe. InnoDB is the default for good reason.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Tuning MySQL for a VPS is about understanding your workload&#8217;s working set and allocating memory accordingly. The configuration templates above are starting points \u2014 measure, adjust, and remeasure. When choosing a VPS for your database workload, <a href=\"https:\/\/virtualserversvps.com\/#providers\">check out the best VPS performance specs<\/a> to find providers that offer the RAM-to-price ratio that matches your database&#8217;s working set. A database with a 2 GB working set on a 4 GB VPS will outperform the same database on a 2 GB VPS with NVMe storage, because the data lives in RAM where it belongs.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>MySQL and MariaDB are the most popular database engines for VPS-hosted web applications, but their default configurations are designed for dedicated servers with abundant RAM. On a 1\u20134 GB VPS,&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":0,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-965","post","type-post","status-publish","format-standard","hentry","category-performance-optimization"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM - Virtual Servers VPS Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM\" \/>\n<meta property=\"og:description\" content=\"MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM\" \/>\n<meta property=\"og:url\" content=\"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/\" \/>\n<meta property=\"og:site_name\" content=\"Virtual Servers VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-24T22:37:51+00:00\" \/>\n<meta name=\"author\" content=\"Virtual-Servers-Vps-Editor\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Virtual-Servers-Vps-Editor\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/\",\"url\":\"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/\",\"name\":\"MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM - Virtual Servers VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#website\"},\"datePublished\":\"2026-08-24T22:37:51+00:00\",\"author\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0\"},\"breadcrumb\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/virtualserversvps.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#website\",\"url\":\"https:\/\/virtualserversvps.com\/blog\/\",\"name\":\"Virtual Servers VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/virtualserversvps.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0\",\"name\":\"Virtual-Servers-Vps-Editor\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g\",\"caption\":\"Virtual-Servers-Vps-Editor\"},\"sameAs\":[\"https:\/\/virtualserversvps.com\/blog\"],\"url\":\"https:\/\/virtualserversvps.com\/blog\/author\/virtualserversvps\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM - Virtual Servers VPS Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/","og_locale":"en_US","og_type":"article","og_title":"MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM","og_description":"MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM","og_url":"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/","og_site_name":"Virtual Servers VPS Blog","article_published_time":"2026-08-24T22:37:51+00:00","author":"Virtual-Servers-Vps-Editor","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Virtual-Servers-Vps-Editor","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/","url":"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/","name":"MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM - Virtual Servers VPS Blog","isPartOf":{"@id":"https:\/\/virtualserversvps.com\/blog\/#website"},"datePublished":"2026-08-24T22:37:51+00:00","author":{"@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0"},"breadcrumb":{"@id":"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/virtualserversvps.com\/blog\/mysql-mariadb-performance-tuning-low-ram-vps\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/virtualserversvps.com\/blog\/"},{"@type":"ListItem","position":2,"name":"MySQL and MariaDB Performance Tuning for VPS Environments with Limited RAM"}]},{"@type":"WebSite","@id":"https:\/\/virtualserversvps.com\/blog\/#website","url":"https:\/\/virtualserversvps.com\/blog\/","name":"Virtual Servers VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/virtualserversvps.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0","name":"Virtual-Servers-Vps-Editor","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g","caption":"Virtual-Servers-Vps-Editor"},"sameAs":["https:\/\/virtualserversvps.com\/blog"],"url":"https:\/\/virtualserversvps.com\/blog\/author\/virtualserversvps\/"}]}},"_links":{"self":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/965","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/comments?post=965"}],"version-history":[{"count":1,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/965\/revisions"}],"predecessor-version":[{"id":966,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/965\/revisions\/966"}],"wp:attachment":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/media?parent=965"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/categories?post=965"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/tags?post=965"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}