ECI: Speed Profiles
The purpose of a Speed Profile is to control the plugins automated functions. We want to control the plugins actions to avoid problems with servers, especially shared servers. Speed Profiles allow us to create multiple profiles for testing and there are some default profiles installed when activating the plugin. However the real idea is to configure a single Speed Profile that suits your WordPress website and will be applied to all projects you create with this plugin. The ability to apply different profiles to each project still exists, giving flexability should you require that.
Video Tutorial
Key Information
- Use speed profiles to control how fast everything happens manually or automatically
- You can create a speed profile and configure it for each project or use one profile for many
Features
Not all features apply to all speed profile types i.e. Event Delay does not apply to the manual method or full speed.
Event Delay
I can create tools to allow a more natural and random delay in events if required. For now the Event Delay forces the plugin to wait a number of seconds before allow another event to be triggered. Set it as low or high as you want, but keep in mind that many events in a short period if time may upset your server!
Create #
This is the number of posts/pages that the plugin will create with a Create event is actioned. Try not to make this too high if you are using low cost hosting. My own hosting is not keen on processes which last 30 seconds but that would require thousands of posts to be made in a single event.
Import #
This is the number of rows to import to your project database in a single Import event. Like any other event you should not set the number too high unless you control your own server. You may set the number higher than the “Create #” value because the plugin only executes a single SQL query per row/record. Far more happens in WordPress, not this plugin, when a single post is being created. In short, you will be safe to import data at a faster rate than creating posts.
Update #
The number of posts to update, a low priority action if you have Update On View activated, otherwise Update events are required to apply any changes to old posts. The Update On View feature triggers an update to a post when it is being viewed. The viewer has no idea it is happening and it saves your server from going through more large long processes of changing all your posts. If you disable Update On View, then this “Update #” value will come in play when Update events are triggered.
Future Events List
This list will show you the events due, mainly based on your Event Delay value. It is for information purposes only. An important feature which is a very new approach in automated events is the Priority Actions column. More about that column is explained below.
Priority Action
The priority action column indicates the event that the plugin will carry out. However it may also carry out other events i.e. if the plugin has not finished importing data on an automated basis, but runs out of records in the project database table during a Post Creation event, it will then switch to do some data importing during the event. Looking at it this way, Ive created the term “event” to mean multiple possible operations. The key thing to know is that there must always be restrictions, so for this concept to work properly the plugin has to decide how long has to go in terms of processing, when carrying an event out.