Skip to main content

Importing Content Will Use Computer Resources

The ability to copy comments and posts into a blog - and even between blogs - is a useful option in Blogger.

Some blog owners take the "Export Blog" / "Import Blog" wizards too casually. Most computer owners enjoy multitasking - and multitasking, between various online activities which involve your personal involvement, can increase productivity.

The process of importing comments and posts, into a Blogger blog, does not involve your personal involvement - and does not work well during multitasking. Multitasking will actually slow the import process down - and what might take mere minutes can take hours, or days.

Too many computer owners, accustomed to doing several things at once on a given computer, may casually add the process of importing a set of comments and posts into a blog, as just one more task.

Most Internet tasks - such as chatting with family and friends, reading and sending email, and web surfing in general - run at your speed. If you're busy chatting, the email task sits idle in the background. Likewise if you are reading email, you may not be doing a lot of web surfing.

The task of importing comments and posts into a blog, on the other hand, runs without your involvement. On a well maintained computer, with nothing else to do, a moderate sized ".xml" file can take just minutes to upload to your blog. The key here is "nothing else to do".

There are various computer activities.
  • Reading and writing content, locally ("disk" activity).
  • Reading and writing content, using the Internet ("network" activity).
  • Processing content read, into content written ("CPU" activity).
The Export / Import tasks involve all 3 activities heavily, plus require a fourth crucial resource - memory. Export / import tasks do not require your involvement - and are limited by the least available of the 4 above resources (which is still faster than with you being involved).

Since you do not have anything to do while a blog is being exported to a local file - or a local file is being imported to a blog - you may be tempted to spend your time chatting, reading / writing email, or surfing the web.

If you have only one computer, this may be a bad decision. Anything that you may do, which involves your action on the computer - chatting with family and friends, reading and sending email, and web surfing in general - is going to require CPU, disk, memory, and / or network resources.

Anything that competes with an export or import task, for resources, is going to make the export / import task run slower. In extreme cases, a task that should take minutes can end up taking hours - or even days - to complete.

One other way to make the import process run slower is to publish posts, as you import. This will, at best, cut import speed in half - and probably have a worse effect. Resist the temptation to select "Automatically publish all imported posts", when importing.

The next time that you export your blog to a local file - or import from a local file to a blog - try using a second computer - or take the afternoon off from any Internet activity. And close all browser tabs and windows, excepting the one where you are actually running the export or import.

If you lighten the load, of all non essential tasks, you may find that the export / import task runs faster than you expected - and you may be able to get back to your chatting with family and friends, reading and sending email, and web surfing in general, a lot sooner than you would have expected.

Comments

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.