Bingology - The Blog of Aaron 'BingoBoingo' Rogier

ADD7A9A28F85E5EF1F51904F309BB8D7F3251143
About | Contact | PGP Public Key | Archive
« Censorship Resistance In 2018 - An Introduction
Peso Watch November 2018 »

Collected Lessons About MP-WP After Rebuilding This Blog Again

After rebuilding this blog following a small disaster I allowed to happen a number of lessons about MP-WP have been collected:

The Quality of MP-WP Documentation Has Improved Through Addition

There are now several guides to setting up MP-WP. The most recent addition by billymg offers the clearest instructions for getting MP-WP running on a Rockchip and alleviating certain persistent pains. The esthlos guide remains solid in the general case. Lobbes covers yet more interesting issues to consider.

One Simple MySQL Configuration Tweak Saves Lots Of RAM

By the default configuration MySQL will default to using the InnoDB engine to store everything. This come with substantial RAM usage spent on ACID compliance and caching. In the read often write infrequently environment of blog substrate InnoDB is overkill and on a machine with a hard RAM budget like the RockChip, MyISAM appears to be a safer choice. RAM allocated to MySQL has dropped from 1.3 GB in my last stack to ~100 MB in the present stack.

In my.conf simply add

default-storage-engine = MyISAM

In the

[mysqld]

section of my.conf wherever it happens to live on your system. Probably /etc/mysql though there may be others possibilities.

Substantial MP-WP Funnctionality Needs Apache2

In my last stack I used lighttpd. Pingbacks never got sent. In this stack built on apache2 pingbacks are being sent. Substantial reading would likely be necessary to unveil what other MP-WP functions are dysfunctional on alternate httpd software.

One still further bonus is that Apache2 with mod_php is sitting in less RAM than lighttpd and it's php-fpm instances.

Edit This One File To Get A Civilized Archive Page

To get an archives page that looks like this you can use this line in your archives.php file in the default theme:


		<?php wp_get_archives( array( 'type' => 'postbypost' ) ); ?>

Conclusions

The rebuilding sucks and is a reminder that discounting the need for frequent backups doesn't kill the need. On the plus side, after this rebuild there is a whole lot more breathing room on the RockChip.

This entry was posted on Monday, November 19th, 2018 at 1:55 a.m. and is filed under Computing. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply

Click here to cancel reply.

 

It's still a pleasure to read bb prose. Both well researched and well written...

- Mircea Popescu

Recent Posts

  • Uruguay-SSR And The Hallucinated Seige
  • Introducing "The Montevideo Standard"
  • Qntra: A Plan For Action
  • A Homework Assignment From Diana_Coman: Trawling Ancient PMs Seeking What Worked For Early Qntra And Where I'm At On Scripting A Conversion Engine
  • Outreach Automation: A Call For Bids
  • Week 6 2020 Review - With Some Reflections On The Subject Of Feedback And Encountering Bots Blogging For Bots Nest
  • Photos From The Archives - January 20, 2011
  • Week 5 2020 Review - A Start To A Start
  • An Onramp For Contributing To Qntra - On Qntra
  • Week 4 2020 Review - Turning To Qntra

Recent Comments

  • Joe on Sports Team Fandoms as a Model Organism for Understanding Discourse
  • Alaskan Thunder Fuck on That One Agricultural Product And Uruguay
  • Aaron 'BingoBoingo' Rogier on Qntra: A Plan For Action
  • Aaron 'BingoBoingo' Rogier on Some FG Samples And Test Results
  • Mohammed nawar on Some FG Samples And Test Results
  • BetrugsRuehrerVow on Ceviche Theory And Practice
  • Aaron 'BingoBoingo' Rogier on Introducing "The Montevideo Standard"

Feeds

  • Posts RSS
  • Comments RSS


Tip Jar: 15eVXAW7k8uKc5moDFUSc9Y3jmHFAenNXo