Improve performance by operating locally

[bobbingwide]

Currently the createapi2.php file ( in oik-batch ) runs as a client server process.
Processing would be more efficient if run as a batch process, using a local database.

Proposed solution

Use oik-batch's oik-wp.php to invoke WordPress locally against the oik-shortcodes plugin passing the name of the plugin/theme to load, previous version etc.

oik-shortcodes.php will respond to the action hook "run_oik-shortcodes.php"

[bobbingwide]

When running PHP from the command line the PHP ini value max_execution_time defaults to 0 - no limit - but calls to set_time_limit() will actually change the value. These calls should not be performed.

[bobbingwide]

See also bobbingwide/oik-batch#4

[bobbingwide]

When running locally we need to ensure we don't re-use data created for a previous file or API when creating the next one. The $_POST array and some global variables need to be reset after each file, class or API is created or updated.

As an aside. WordPress does not behave at all well when there are 6 million post_meta rows. I had up to 4,000 post_meta records per post. Oops!

[bobbingwide]

oiksc_update_oik_hook() needs to be functional when running locally, otherwise hooks won't be created.

[bobbingwide]

Need to ensure _oik_api_hooks post meta data is updated even when the $oikai_hook array is empty.

[bobbingwide]

Performance when running locally can be improved by only processing the functions that have actually changed. The average number of functions per file in WordPress is 15. Currently if the file is slightly changed we are reprocessing every function/method.

[bobbingwide]

I believe this is safe to close now.