« What do you want to see on the Diskeeper Blog? | Main | What Does Diskeeper Mean By "RealTime"? »

October 26, 2006

InvisiTasking and BOINC

If you're reading this blog you probably have a good idea of what InvisiTasking is and what it does already. If not, you can read some of the earlier blogs on that subject for review, or check out an interview I did on Let's Talk Computers (http://www.letstalkcomputers.com/guests/diskeeper/invisitask/index.htm) or Computer Outlook (http://www.computeroutlook.com/dailyshows.php). BOINC is an acronym for Berkeley Open Infrastructure for Network Computing (http://boinc.berkeley.edu/).

While the two technologies are very different in their application, they do share the same principle. Both seek to leverage under-utilized computing power to do something positive.

BOINC is the backbone of numerous science research projects (a popular one is the SETI@home project). The key difference is that BOINC is a grid computing application (distributed computing). It uses wasted resources from an unlimited number of PCs across the internet (volunteer computing). It also offers distributed computing within a company network. InvisiTasking is a closed, single computer technology that does not communicate outside the computer and acts as the backbone of Diskeeper 2007. InvisiTasking is designed specifically for enterprise organizations, with a design focus on transparency of operation for applications used for business/security/productivity on a given computer. In short, they have different infrastructures and purposes.

BOINC also allows a system to run multiple BOINC-based applications concomitantly. InvisiTasking, for it's part, will behave similarly when other programs are built on that technology. Just as BOINC supports the SETI@home project as well as a project to aid in climate prediction, InvisiTasking will support simultaneous real-time defragmentation and, perhaps, a real-time anti-malware scan or file backup or database performance script.

For those, like myself, who contributed to the SETI@home project over the past years (there were 5.4 million volunteers), you knew that it used to run when your screen saver was initiated, much like a popular old Diskeeper feature. The brilliant folks on the BOINC project evolved their technology in parallel (though completely unrelated) with our brilliant R&D team here. The primary reason we evolved our older methodologies into InvisiTasking, is likely the same reason BOINC was introduced - to take better advantage of wasted resources -something screen saver mode was not effective enough at solving.

One thing we became aware of, in field testing, was that InvisiTasking was so resource sensitive that systems running BOINC applications took priority over Diskeeper's defragmentation. However, you don't need to choose between practical benefit for your computer and doing good for mankind.

If you are running SETI@hone or other BOINC applications, you'll want to make adjustments. There are two ways to tweak your computer to allow both programs to run harmoniously. The easiest (recommended) option is to alter BOINC. You can choose to operate as either a "Single User" or "Shared" rather than "As a Service" - and still use screensaver mode. If you do run it as a Service, you can edit your preferences to cap resources usage. BOINC also has a "snooze" button.

The other option (not recommended) is to make changes that alter InvisiTasking's behavior. If you do this, you are de-sensitizing InvisiTasking, so we recommend that you may want to consider disabling Diskeeper during certain periods using the graphical Automatic Defragmentation Timeline control. If you are a customer, Tech Support can advise you on this. Our FAQs may also include this information in the future.

Posted by Michael at October 26, 2006 08:55 PM

Comments

I run a similiar distributed computing project called GIMPS and it runs at 'Idle' CPU priority, the lowest CPU prioirity possible on windows xp. The problem is that even if it is running at idle priority, inivisitasking will not happen because it does not run according to whether it gets a cpu cycle or not, it actually looks at the CPU usage, and if it is too high of a percentage, it will not run automatic defrag functions.

How do you modify the behavior of invisitasking so that GIMPS and it can work well together?

Thank you

Posted by: danTheman at November 4, 2006 06:41 PM

Hi Dan,

Contact our Tech Support staff at tech_suppport@diskeeper.com for the solution.

There are a number of similar grid projects out there. World Community Grid software is another such example. In each case the solution from Tech Support will apply.

Posted by: Michael at November 6, 2006 10:38 PM

Your article is very informative and helped me further.

Thanks, David

Posted by: davidvogt at February 3, 2007 09:27 PM

Hello, I am having the same problem with auto defrag not running because I am running a distributed computing project in the backround. what is the solution for this problem please?
Perhaps it should be publicly posted for everyone to see. i'm sure many people are having this problem.

Thanx,
Rob

Posted by: Rob at February 4, 2008 07:49 AM

HI Rob,

InvisiTasking in an upcoming Diskeeper release will address this. Until that is available, Technical Support can assist you. Please email them - tech_suppport@diskeeper.com.

Posted by: Michael at February 7, 2008 09:24 PM

Can you provide details on which version has the updated InvisiTask to address the auto defrag issue. I am running 2008 build 12.0.758.0 and have similar issues. I have been digging around the registry and have found AutoPriority and ManualPriority entries, but I am afraid to touch them yet. Are these entries tunable?

Posted by: Lou at July 22, 2008 09:57 PM

Hi Lou,

Please contact support. They can provide the specific steps.

Posted by: michael at July 29, 2008 02:26 AM

Post a comment




Remember Me?