2,000,000,000,000 WordPress posts, is it possible? Simple answer, Yes. The days of 2GB size limit on file systems are gone. Now, you can literally have unlimited entries on almost everywhere if your hardware can support it. So I’m gonna change the question into this: 2,000,000 WordPress posts, Should I have it? To decide whether WordPress … Read more
I recommend you to read this article W3 Total Cache -Plugin: The Complete Settings Guide, it’s a great tutorial to manually setup your w3tc. And when you saving your settings remember to flush your cache because if you don’t Google Pagespeed will test it on the old cached files.. You can try to add this … Read more
For each translation file, WordPress has to unpack it, then each entry will be converted into an Translation_Entry object. The short string “caller_get_posts” is deprecated. Use “ignore_sticky_posts” instead. will need three times more memory when it is translated: ‘”caller_get_posts” is deprecated. Use “ignore_sticky_posts” instead.’ => Translation_Entry::__set_state(array( ‘is_plural’ => false, ‘context’ => NULL, ‘singular’ => ‘”caller_get_posts” … Read more
I could be wrong, but I don’t think your queries are the problem here. Seeing the result “36 queries in 8.291 seconds” is scary, but that only measures the time in between the start of the first query and the completion of the last query. There are a lot of other things in there slowing … Read more
The apache process memory amount you talk about (80 to 120 MB per process) can be split into two reasons. Apache WordPress Apache You can optimize apache by only loading the number of modules you need and other optimization tweaks that will reduce the memory. If you have not optimized that yet, give it some … Read more
Well website (WordPress) page speed and load depends on many things. MySql Queries Image optimisation Css files (more cs files more page load and page speed time). Javascript files ( more js files more page load and page speed time). Defer parsing of JavaScript Minify JavaScript Minify CSS Enable gzip compression Leverage browser caching Minimize … Read more
None. The whole source of wp_create_user() is: function wp_create_user($username, $password, $email=””) { $user_login = esc_sql( $username ); $user_email = esc_sql( $email ); $user_pass = $password; $userdata = compact(‘user_login’, ‘user_email’, ‘user_pass’); return wp_insert_user($userdata); } It just calls insert version almost immediately, basically a shorthand wrapper. As for why it exists – core works in mysterious ways … Read more
Meanwhile, I found some plugins and tools that can help with this: Query Monitor Laps Debug Bar with some add-ons(Slow Actions, Rewrite Rules, etc.) If you really wanna go deep, try using Webgrind. Not the most friendly tool, but it’ll do the job. Be aware that some of this tools will also have an impact … Read more
Basic answer to “what plugin” would probably be W3 Total Cache. It is one of the most functional and actively developed plugins at moment. However complete performance chain is much longer that WordPress plugin alone can handle. Web server (Apache or something else) configuration (response time, time to first byte, headers). Database (time spent processing … Read more
Update: The reason the query is being logged is it doesn’t use an index. The query time is 0, i.e. it actually executes fast. You can unset the “log-queries-not-using-indexes” option if you don’t want these to be logged. The wp_options table has no index on autoload (it now should, it was added to WP core … Read more